← previous blocknext block →recent activity
Analyzing
Block #82,341,267
22 transactions · 17 stateful · 2026-06-19 16:16:00 UTC
Parallelism
77/100
Blocked
59%
Avg conflicts / tx
0.95
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,341,267 · 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
1w02w13w04w27w08w19w210w311w414w216w320w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffa7d0a4…b10a
0x40c49f…2af0
10 touches
10 conflicts
0x5581d709…ab77
0x2a68ba…90c5
8 touches
6 conflicts
0x957c875f…b3f9
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x08913286…f0df
0x34b655…2a6f
6 touches
3 conflicts
0xb2fa1675…4e07
0x34b655…2a6f
6 touches
3 conflicts
0xc34c34a6…b46f
0x34b655…2a6f
4 touches
1 conflict
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: 0x40c49f17…d22af0
10 conflicts on slot 0xffa7d0a419…63b10a
Audit this contract →
← previous block·next block →recent activity