← previous blocknext block →recent activity
Analyzing
Block #84,496,984
18 transactions · 17 stateful · 2026-06-29 16:05:34 UTC
Parallelism
67/100
Blocked
41%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,496,984 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w18w210w112w214w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x366f651e…6100
0x34b655…2a6f
6 touches
3 conflicts
0x251766cd…7892
0x34b655…2a6f
6 touches
3 conflicts
0xab86573c…682e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x85a88798…f85e
0x34b655…2a6f
4 touches
1 conflict
0x9180af06…5ac6
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
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 0x366f651e17…e36100
Audit this contract →
← previous block·next block →recent activity