← previous blocknext block →recent activity
Analyzing
Block #84,571,724
16 transactions · 13 stateful · 2026-06-30 00:24:29 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,571,724 · 16 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
3w04w15w06w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2207d3d…59ce
0x34b655…2a6f
8 touches
6 conflicts
0x801058a8…5bc3
0x34b655…2a6f
6 touches
3 conflicts
0x19df8d7c…4259
0x34b655…2a6f
4 touches
1 conflict
0x1a929a3d…1672
0x34b655…2a6f
4 touches
1 conflict
0x329f2f7d…dcff
0x34b655…2a6f
4 touches
1 conflict
0x374fc18a…6998
0x34b655…2a6f
4 touches
1 conflict
0x41a9e744…5647
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
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
6 conflicts on slot 0xc2207d3d4e…b259ce
Audit this contract →
← previous block·next block →recent activity