← previous blocknext block →recent activity
Analyzing
Block #100,126,013
15 transactions · 13 stateful · 2026-08-29 07:34:46 UTC
Parallelism
73/100
Blocked
46%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,126,013 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w08w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ac040c1…8224
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xedee7e09…6888
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
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)
3 conflicts on slot 0x9ac040c10e…a08224
Audit this contract →
← previous block·next block →recent activity