← previous blocknext block →recent activity
Analyzing
Block #81,877,249
14 transactions · 11 stateful · 2026-06-17 12:39:46 UTC
Parallelism
86/100
Blocked
27%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #81,877,249 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w18w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa496646a…41a4
0x34b655…2a6f
4 touches
1 conflict
0xd9aed890…c52f
0x34b655…2a6f
4 touches
1 conflict
0xe5e2826c…bb1b
0x34b655…2a6f
4 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x1175233a…64e7
0x34b655…2a6f
4 touches
1 conflict
0x261c40aa…b133
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
1 conflict on slot 0xa496646afc…ed41a4
Audit this contract →
← previous block·next block →recent activity