← previous blocknext block →recent activity
Analyzing
Block #82,018,604
25 transactions · 17 stateful · 2026-06-18 04:24:02 UTC
Parallelism
84/100
Blocked
53%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,018,604 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w07w18w19w010w111w212w321w022w123w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x24b18e…3301
8 touches
6 conflicts
0x771a3650…01cd
0x3bd359…433a
8 touches
6 conflicts
0x797464db…e15a
0x788571…8888
8 touches
6 conflicts
0xa743c8dd…ebf2
0x788571…8888
8 touches
6 conflicts
0x00000000…0001
0x24b18e…3301
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x388f889f…a655
0x34b655…2a6f
6 touches
3 conflicts
0x75f928fc…0465
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: 0x24b18eb6…733301
6 conflicts on slot 0x0000000000…000000
Audit this contract →
← previous block·next block →recent activity