← previous blocknext block →recent activity
Analyzing
Block #82,272,035
21 transactions · 20 stateful · 2026-06-19 08:34:13 UTC
Parallelism
76/100
Blocked
55%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,272,035 · 21 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
1w02w13w24w17w08w19w210w311w412w013w114w216w018w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xaa7ee7…f0e4
10 touches
10 conflicts
0x08913286…f0df
0x34b655…2a6f
6 touches
3 conflicts
0xe8e68d63…92a9
0xd32edf…ff58
5 touches
3 conflicts
0x25de453d…9573
0x34b655…2a6f
4 touches
1 conflict
0x6f6fc26c…3e34
0x34b655…2a6f
4 touches
1 conflict
0xa678cd56…4fab
0x34b655…2a6f
4 touches
1 conflict
0xa67ee943…0936
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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: 0xaa7ee7ce…aff0e4
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity