← previous blocknext block →recent activity
Analyzing
Block #82,725,256
34 transactions · 28 stateful · 2026-06-21 11:01:32 UTC
Parallelism
82/100
Blocked
54%
Avg conflicts / tx
1.15
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #82,725,256 · 34 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
1w02w16w08w09w111w212w313w214w315w317w427w328w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
10 touches
10 conflicts
0x26abe30c…f680
0x34b655…2a6f
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x5d46e6a0…5ed9
0x40c49f…2af0
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x9fb55ee7…8ecc
0xa6afd3…d132
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc68d6f14…bdde
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
10 conflicts on slot 0x08913286f9…0ff0df
Audit this contract →
← previous block·next block →recent activity