← previous blocknext block →recent activity
Analyzing
Block #84,610,175
12 transactions · 9 stateful · 2026-06-30 04:40:43 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,610,175 · 12 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
5w06w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2207d3d…59ce
0x34b655…2a6f
6 touches
3 conflicts
0x7b7a78ce…a432
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2ae48bbe…579c
0x34b655…2a6f
4 touches
1 conflict
0x5f447bf3…57c7
0x34b655…2a6f
4 touches
1 conflict
0x6cb97876…d1b0
0x34b655…2a6f
4 touches
1 conflict
0x712f13a9…bee0
0x34b655…2a6f
4 touches
1 conflict
0x86a6e399…369e
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 0xc2207d3d4e…b259ce
Audit this contract →
← previous block·next block →recent activity