← previous blocknext block →recent activity
Analyzing
Block #84,459,882
22 transactions · 21 stateful · 2026-06-29 11:57:58 UTC
Parallelism
55/100
Blocked
57%
Avg conflicts / tx
2.18
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #84,459,882 · 22 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w69w710w811w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
20 touches
45 conflicts
0xa4658f5c…b257
0x34b655…2a6f
4 touches
1 conflict
0x7a2031c8…c223
0x34b655…2a6f
4 touches
1 conflict
0xa1ddcb83…bc9f
0x34b655…2a6f
4 touches
1 conflict
0xac61d3a4…7da8
0x34b655…2a6f
4 touches
1 conflict
0xbbb9fa77…d121
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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: 0xd637b38f…c64160
45 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity