← previous blocknext block →recent activity
Analyzing
Block #101,066,200
47 transactions · 36 stateful · 2026-09-01 14:29:24 UTC
Parallelism
81/100
Blocked
64%
Avg conflicts / tx
1.47
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #101,066,200 · 47 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w210w111w212w313w417w529w231w634w638w339w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3483764…f296
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…0018
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0028
0x1b6862…e19c
12 touches
15 conflicts
0x6518642d…456f
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 0xc34837646d…35f296
Audit this contract →
← previous block·next block →recent activity