← previous blocknext block →recent activity
Analyzing
Block #84,523,476
13 transactions · 12 stateful · 2026-06-29 19:02:16 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,523,476 · 13 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
1w02w16w08w09w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf28082df…312c
0x34b655…2a6f
6 touches
3 conflicts
0xf412c531…d397
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x6b47245e…a342
0x34b655…2a6f
4 touches
1 conflict
0x813e5204…591d
0x34b655…2a6f
4 touches
1 conflict
0x86977b3d…a9c4
0x34b655…2a6f
4 touches
1 conflict
0xb9b4eff6…c3ef
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 0xf28082df38…4b312c
Audit this contract →
← previous block·next block →recent activity