← previous blocknext block →recent activity
Analyzing
Block #101,308,356
18 transactions · 16 stateful · 2026-09-02 10:47:55 UTC
Parallelism
67/100
Blocked
56%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,308,356 · 18 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
1w02w13w08w010w211w112w213w314w415w416w517w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x394c3833…b4ac
0x1b6862…e19c
8 touches
6 conflicts
0xa0add0e6…0797
0xd32edf…ff58
7 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xe708c9f4…b505
0x34b655…2a6f
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: ShMonad (shMON)
6 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity