← previous blocknext block →recent activity
Analyzing
Block #84,500,660
31 transactions · 24 stateful · 2026-06-29 16:30:06 UTC
Parallelism
81/100
Blocked
54%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,500,660 · 31 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w010w011w112w215w316w117w018w119w220w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x350c7a71…8d82
0x34b655…2a6f
8 touches
6 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
8 touches
6 conflicts
0xec85756f…0ba2
0x34b655…2a6f
8 touches
6 conflicts
0x51087f5a…61f7
0x34b655…2a6f
8 touches
6 conflicts
0x9ba2e28c…ac19
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0002
0xd637b3…4160
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 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: Perpl
15 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity