← previous blocknext block →recent activity
Analyzing
Block #101,062,337
40 transactions · 37 stateful · 2026-09-01 14:09:54 UTC
Parallelism
60/100
Blocked
68%
Avg conflicts / tx
2.67
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #101,062,337 · 40 txs across 16 waves · depth 16
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
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w510w518w619w720w721w823w227w828w934w1037w1338w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
18 touches
36 conflicts
0xfac61869…a55b
0x1b6862…e19c
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…0015
0x1b6862…e19c
18 touches
36 conflicts
0x9911858e…0bf3
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0018
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0028
0x1b6862…e19c
16 touches
28 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…000013
Audit this contract →
← previous block·next block →recent activity