← previous blocknext block →recent activity
Analyzing
Block #84,610,211
13 transactions · 13 stateful · 2026-06-30 04:40:58 UTC
Parallelism
69/100
Blocked
23%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,610,211 · 13 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
3w08w19w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x744e0a36…70f7
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xfc366eef…6209
0x34b655…2a6f
6 touches
3 conflicts
0x41d3bfa5…523e
0x34b655…2a6f
4 touches
1 conflict
0x4546ebad…b908
0x34b655…2a6f
4 touches
1 conflict
0x6b47245e…a342
0x34b655…2a6f
4 touches
1 conflict
0x7dbd84bc…b2a6
0x34b655…2a6f
4 touches
1 conflict
0x80a90bf4…37e4
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 0x744e0a3655…6d70f7
Audit this contract →
← previous block·next block →recent activity