← previous blocknext block →recent activity
Analyzing
Block #101,310,031
36 transactions · 33 stateful · 2026-09-02 10:56:20 UTC
Parallelism
67/100
Blocked
79%
Avg conflicts / tx
2.44
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #101,310,031 · 36 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w111w212w333w1034w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0013
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0015
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…001d
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…002d
0x1b6862…e19c
18 touches
36 conflicts
0x394c3833…b4ac
0x1b6862…e19c
18 touches
36 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
18 touches
36 conflicts
0x5cb4a7a5…e0bc
0xd32edf…ff58
17 touches
36 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)
36 conflicts on slot 0x0000000000…000012
Audit this contract →
← previous block·next block →recent activity