← previous blocknext block →recent activity
Analyzing
Block #81,627,973
11 transactions · 9 stateful · 2026-06-16 08:58:51 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #81,627,973 · 11 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
2w09w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe732567d…b65d
0x34b655…2a6f
4 touches
1 conflict
0x41be9e75…9773
0x34b655…2a6f
4 touches
1 conflict
0x82f1c92a…08a6
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2391cba8…9602
0x34b655…2a6f
2 touches
0 conflicts
0x3214fb6a…0f14
0x34b655…2a6f
2 touches
0 conflicts
0x50b57ae2…fac6
0x34b655…2a6f
2 touches
0 conflicts
0xaf78779d…317d
0x34b655…2a6f
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 0xe732567db9…26b65d
Audit this contract →
← previous block·next block →recent activity