← previous blocknext block →recent activity
Analyzing
Block #84,514,218
22 transactions · 21 stateful · 2026-06-29 18:00:35 UTC
Parallelism
86/100
Blocked
33%
Avg conflicts / tx
0.55
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,514,218 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w111w212w013w114w015w116w218w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xfff39462…a61b
0x34b655…2a6f
6 touches
3 conflicts
0x7c6d3d6d…9deb
0x34b655…2a6f
6 touches
3 conflicts
0x2df5ccba…a51e
0x34b655…2a6f
4 touches
1 conflict
0x3766925b…76fe
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49b0842d…0a93
0x34b655…2a6f
4 touches
1 conflict
0x6e2becf4…0c5f
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity