← previous blocknext block →recent activity
Analyzing
Block #84,060,229
31 transactions · 27 stateful · 2026-06-27 15:35:28 UTC
Parallelism
77/100
Blocked
63%
Avg conflicts / tx
1.61
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,060,229 · 31 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w37w48w09w110w211w312w413w514w622w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
14 touches
21 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x489bff18…82f3
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
10 touches
10 conflicts
0x117f1699…b264
0xa6afd3…d132
10 touches
10 conflicts
0x8726ff39…3be8
0x34b655…2a6f
10 touches
10 conflicts
0x763dd151…d9de
0xa6afd3…d132
10 touches
10 conflicts
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
21 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity