← previous blocknext block →recent activity
Analyzing
Block #102,017,263
19 transactions · 17 stateful · 2026-09-04 22:19:25 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,017,263 · 19 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
3w04w15w27w18w29w310w411w514w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9256b810…52ca
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001b
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002b
0x1b6862…e19c
12 touches
15 conflicts
0x2ac58b6a…8a92
0xd32edf…ff58
11 touches
15 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: ShMonad (shMON)
15 conflicts on slot 0x9256b81014…fb52ca
Audit this contract →
← previous block·next block →recent activity