← previous blocknext block →recent activity
Analyzing
Block #82,019,402
23 transactions · 17 stateful · 2026-06-18 04:29:22 UTC
Parallelism
78/100
Blocked
53%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,019,402 · 23 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
1w02w13w24w011w012w114w115w016w117w218w319w121w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0x24b18e…3301
10 touches
10 conflicts
0xa743c8dd…ebf2
0x788571…8888
10 touches
10 conflicts
0x00000000…0000
0x24b18e…3301
10 touches
10 conflicts
0x771a3650…01cd
0x3bd359…433a
10 touches
10 conflicts
0x797464db…e15a
0x788571…8888
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x4e7eb462…b2ad
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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: 0x24b18eb6…733301
10 conflicts on slot 0x0000000000…000001
Audit this contract →
← previous block·next block →recent activity