← previous blocknext block →recent activity
Analyzing
Block #105,636,068
21 transactions · 17 stateful · 2026-09-17 15:02:55 UTC
Parallelism
67/100
Blocked
65%
Avg conflicts / tx
0.76
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,636,068 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w18w39w413w514w615w116w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59658b83…2228
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0xaa63700d…2df8
0xd32edf…ff58
7 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 0x59658b837a…cb2228
Audit this contract →
← previous block·next block →recent activity