← previous blocknext block →recent activity
Analyzing
Block #84,362,572
18 transactions · 13 stateful · 2026-06-29 01:09:29 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,362,572 · 18 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
2w03w16w07w18w215w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f7ad3a0…de3b
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x5f3fc680…f989
0x34b655…2a6f
4 touches
1 conflict
0x619f5683…5bd4
0x34b655…2a6f
4 touches
1 conflict
0x69aea55e…a6c5
0x34b655…2a6f
4 touches
1 conflict
0x753da1ce…6bbd
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 0x3f7ad3a0be…58de3b
Audit this contract →
← previous block·next block →recent activity