← previous blocknext block →recent activity
Analyzing
Block #84,355,410
22 transactions · 16 stateful · 2026-06-29 00:21:41 UTC
Parallelism
82/100
Blocked
31%
Avg conflicts / tx
0.27
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,355,410 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w19w013w217w118w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x28a5dbb8…3ad7
0x34b655…2a6f
6 touches
3 conflicts
0x454d8940…cfe7
0x34b655…2a6f
6 touches
3 conflicts
0x3d4ec808…d43b
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x1951ee47…540f
0x34b655…2a6f
4 touches
1 conflict
0x241e2ea9…bb31
0x34b655…2a6f
4 touches
1 conflict
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0x37773728…f3a4
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 0x28a5dbb865…4d3ad7
Audit this contract →
← previous block·next block →recent activity