← previous blocknext block →recent activity
Analyzing
Block #84,240,774
11 transactions · 9 stateful · 2026-06-28 11:37:54 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,240,774 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x6f58168d…ea24
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x393dfd73…ff57
0x34b655…2a6f
2 touches
0 conflicts
0x395e85be…726c
0x34b655…2a6f
2 touches
0 conflicts
0x43d16f2c…afaf
0x34b655…2a6f
2 touches
0 conflicts
0x4ebafd01…eb37
0x34b655…2a6f
2 touches
0 conflicts
0x5ee17ef5…ab59
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 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity