← previous blocknext block →recent activity
Analyzing
Block #100,809,403
40 transactions · 34 stateful · 2026-08-31 16:57:16 UTC
Parallelism
68/100
Blocked
59%
Avg conflicts / tx
1.95
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #100,809,403 · 40 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w216w317w418w519w620w721w826w328w834w7
- 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…001b
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…002b
0x1b6862…e19c
18 touches
36 conflicts
0x394c3833…b4aa
0x1b6862…e19c
18 touches
36 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
18 touches
36 conflicts
0xd274fc8d…cc69
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