← previous blocknext block →recent activity
Analyzing
Block #84,352,496
43 transactions · 35 stateful · 2026-06-29 00:02:15 UTC
Parallelism
81/100
Blocked
66%
Avg conflicts / tx
1.51
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,352,496 · 43 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
3w04w15w26w37w48w010w111w220w528w529w230w631w632w333w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x454d8940…cfe7
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…0002
0xd637b3…4160
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
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
10 conflicts on slot 0x454d8940c1…fbcfe7
Audit this contract →
← previous block·next block →recent activity