← previous blocknext block →recent activity
Analyzing
Block #82,969,670
22 transactions · 20 stateful · 2026-06-22 14:14:28 UTC
Parallelism
77/100
Blocked
35%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,969,670 · 22 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
1w02w13w04w15w26w37w09w110w220w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74355ed1…eda6
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x36a49c16…89b9
0xc8689a…ee79
8 touches
6 conflicts
0x08913286…f0df
0x34b655…2a6f
8 touches
6 conflicts
0xbbb9fa77…d121
0x34b655…2a6f
8 touches
6 conflicts
0xbd7e0241…07f5
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x34739831…0704
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 0x74355ed1b5…73eda6
Audit this contract →
← previous block·next block →recent activity