← previous blocknext block →recent activity
Analyzing
Block #84,119,644
12 transactions · 10 stateful · 2026-06-27 22:11:15 UTC
Parallelism
58/100
Blocked
40%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,119,644 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x3e505a15…70f8
0x34b655…2a6f
6 touches
3 conflicts
0xebbcae2a…16f8
0x34b655…2a6f
6 touches
3 conflicts
0x8c73d3c9…94fd
0x34b655…2a6f
5 touches
3 conflicts
0x35a7fba8…ca5a
0x34b655…2a6f
4 touches
1 conflict
0x36ce3449…71d4
0x34b655…2a6f
4 touches
1 conflict
0x41c88af9…2373
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity