← previous blocknext block →recent activity
Analyzing
Block #83,660,010
17 transactions · 15 stateful · 2026-06-25 19:06:39 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,660,010 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w25w07w18w29w313w414w515w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x925c118c…a1d8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x580c6fe7…0fe6
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
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
6 conflicts on slot 0x925c118c7b…bea1d8
Audit this contract →
← previous block·next block →recent activity