← previous blocknext block →recent activity
Analyzing
Block #84,105,759
39 transactions · 31 stateful · 2026-06-27 20:38:45 UTC
Parallelism
80/100
Blocked
68%
Avg conflicts / tx
1.97
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,105,759 · 39 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
1w02w13w24w35w46w58w69w510w628w729w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0xe02484a6…c32e
0xc8689a…ee79
14 touches
21 conflicts
0x5df6102c…6494
0xa6afd3…d132
14 touches
21 conflicts
0x2d5c395b…6b5a
0xa6afd3…d132
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
14 touches
21 conflicts
0xb3975d93…b4a2
0x34b655…2a6f
14 touches
21 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
14 touches
21 conflicts
0x19ce481d…6c36
0x34b655…2a6f
14 touches
21 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
28 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity