← previous blocknext block →recent activity
Analyzing
Block #84,460,701
26 transactions · 22 stateful · 2026-06-29 12:03:27 UTC
Parallelism
85/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,460,701 · 26 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
1w02w16w07w114w116w117w219w020w121w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x571cb36d…3b3d
0x34b655…2a6f
6 touches
3 conflicts
0x72e55a59…2a2d
0xa6afd3…d132
4 touches
1 conflict
0x49b0842d…0a93
0x34b655…2a6f
4 touches
1 conflict
0x83863be1…4324
0x34b655…2a6f
4 touches
1 conflict
0x85ac0ab8…a3d8
0x34b655…2a6f
4 touches
1 conflict
0x8e739938…e7ab
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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 0x571cb36db3…a33b3d
Audit this contract →
← previous block·next block →recent activity