← previous blocknext block →recent activity
Analyzing
Block #82,018,631
37 transactions · 24 stateful · 2026-06-18 04:24:13 UTC
Parallelism
73/100
Blocked
58%
Avg conflicts / tx
1.11
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #82,018,631 · 37 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w27w38w417w020w121w222w323w424w525w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
12 touches
15 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x2bf5914f…c75d
0x34b655…2a6f
8 touches
6 conflicts
0x3284d35d…74af
0x34b655…2a6f
8 touches
6 conflicts
0x8fb50369…d3d2
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
15 conflicts on slot 0x08913286f9…0ff0df
Audit this contract →
← previous block·next block →recent activity