← previous blocknext block →recent activity
Analyzing
Block #108,927,289
17 transactions · 15 stateful · 2026-09-29 03:17:48 UTC
Parallelism
59/100
Blocked
53%
Avg conflicts / tx
1.18
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,927,289 · 17 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
2w03w14w25w36w07w08w411w113w014w115w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x0f28fb99…3d2e
0x1b6862…e19c
12 touches
15 conflicts
0xf95d9afb…e6bb
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0056
0x1b6862…e19c
8 touches
6 conflicts
0x744d62c0…0137
0x1b6862…e19c
8 touches
6 conflicts
0xb4836f9e…a9bb
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)
15 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity