← previous blocknext block →recent activity
Analyzing
Block #84,617,371
29 transactions · 25 stateful · 2026-06-30 05:28:38 UTC
Parallelism
72/100
Blocked
64%
Avg conflicts / tx
1.59
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,617,371 · 29 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w37w49w512w013w114w223w624w725w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
12 touches
15 conflicts
0x00000000…002f
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x8d47c9a4…f121
0x1b6862…e19c
10 touches
10 conflicts
0x7c5260f4…bd96
0xa6afd3…d132
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001f
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
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
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity