← previous blocknext block →recent activity
Analyzing
Block #84,514,571
20 transactions · 18 stateful · 2026-06-29 18:02:56 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,514,571 · 20 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
1w02w15w06w17w210w111w316w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c6d3d6d…9deb
0x34b655…2a6f
6 touches
3 conflicts
0x1d381caf…975f
0x40c49f…2af0
4 touches
1 conflict
0xa9db7b4d…2957
0x40c49f…2af0
4 touches
1 conflict
0xd16a1399…18ee
0x40c49f…2af0
4 touches
1 conflict
0xdfc5f346…7b42
0x40c49f…2af0
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x93d680fb…ac21
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0x7c6d3d6daa…059deb
Audit this contract →
← previous block·next block →recent activity