← previous blocknext block →recent activity
Analyzing
Block #84,460,750
25 transactions · 22 stateful · 2026-06-29 12:03:46 UTC
Parallelism
84/100
Blocked
32%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,460,750 · 25 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
2w03w04w15w06w17w18w29w314w020w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a3ae0e3…ac9b
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
4 touches
1 conflict
0x697cf602…a882
0x34b655…2a6f
4 touches
1 conflict
0x6acbd794…a68b
0x34b655…2a6f
4 touches
1 conflict
0x826cce18…251c
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
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 0x3a3ae0e347…b0ac9b
Audit this contract →
← previous block·next block →recent activity