← previous blocknext block →recent activity
Analyzing
Block #106,394,814
40 transactions · 33 stateful · 2026-09-20 06:44:05 UTC
Parallelism
88/100
Blocked
61%
Avg conflicts / tx
0.97
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,394,814 · 40 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w26w07w09w010w112w114w015w116w017w118w120w322w023w126w227w329w131w234w435w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb45d9d6…cb82
0x1b6862…e19c
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x7fcd7ad1…c34c
0xd32edf…ff58
7 touches
6 conflicts
0xbc0d66ec…873c
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
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)
6 conflicts on slot 0xcb45d9d62a…b1cb82
Audit this contract →
← previous block·next block →recent activity