← previous blocknext block →recent activity
Analyzing
Block #101,153,013
24 transactions · 19 stateful · 2026-09-01 21:46:23 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,153,013 · 24 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
1w02w13w24w38w09w413w515w016w518w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6aa624fd…a84c
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x66fa6b64…3b69
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0019
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
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)
10 conflicts on slot 0x6aa624fd35…14a84c
Audit this contract →
← previous block·next block →recent activity