← previous blocknext block →recent activity
Analyzing
Block #101,315,896
21 transactions · 19 stateful · 2026-09-02 11:25:51 UTC
Parallelism
62/100
Blocked
47%
Avg conflicts / tx
0.81
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,315,896 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w310w411w515w516w617w719w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5b10148…e636
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 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 0xd5b1014813…d9e636
Audit this contract →
← previous block·next block →recent activity