← previous blocknext block →recent activity
Analyzing
Block #84,495,947
29 transactions · 24 stateful · 2026-06-29 15:58:38 UTC
Parallelism
83/100
Blocked
58%
Avg conflicts / tx
1.03
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,495,947 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w111w012w113w214w317w219w320w121w222w323w427w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3975d93…b4a2
0x34b655…2a6f
8 touches
6 conflicts
0x56785e37…a197
0x065c9d…c394
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x783b1b39…f907
0xd32edf…ff58
5 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
6 conflicts on slot 0xb3975d9364…28b4a2
Audit this contract →
← previous block·next block →recent activity