← previous blocknext block →recent activity
Analyzing
Block #84,318,604
14 transactions · 13 stateful · 2026-06-28 20:16:20 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,318,604 · 14 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
4w06w07w18w211w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64dc
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe44598b8…501b
0x34b655…2a6f
4 touches
1 conflict
0xe732567d…b65d
0x34b655…2a6f
4 touches
1 conflict
0x3f4dc602…5a18
0x34b655…2a6f
4 touches
1 conflict
0x51f0b5de…18f7
0x34b655…2a6f
4 touches
1 conflict
0x5eeea918…8147
0x34b655…2a6f
4 touches
1 conflict
0x63214e4a…668d
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
1 conflict on slot 0xb3fb9fb561…7664dc
Audit this contract →
← previous block·next block →recent activity