← previous blocknext block →recent activity
Analyzing
Block #84,544,411
13 transactions · 13 stateful · 2026-06-29 21:22:07 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,544,411 · 13 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
5w06w17w211w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xc08384da…ecb7
0x34b655…2a6f
4 touches
1 conflict
0xd1fe26e6…8d31
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x393dfd73…ff57
0x34b655…2a6f
4 touches
1 conflict
0x0aa5b76b…60db
0x34b655…2a6f
4 touches
1 conflict
0xa7e2f1b7…7e6f
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
3 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity