← previous blocknext block →recent activity
Analyzing
Block #82,328,133
27 transactions · 20 stateful · 2026-06-19 14:48:21 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,328,133 · 27 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
1w02w13w14w26w011w212w013w117w221w023w124w225w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x6ccfa398…71a1
0x34b655…2a6f
8 touches
6 conflicts
0xb3c96942…f0fc
0x34b655…2a6f
8 touches
6 conflicts
0xa51de3df…c65a
0x34b655…2a6f
7 touches
6 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x4fe95978…4ea7
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity