← previous blocknext block →recent activity
Analyzing
Block #109,143,888
19 transactions · 17 stateful · 2026-09-29 21:31:37 UTC
Parallelism
42/100
Blocked
71%
Avg conflicts / tx
3
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #109,143,888 · 19 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w913w1014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
22 touches
55 conflicts
0x75e73565…45f5
0x1b6862…e19c
22 touches
55 conflicts
0x00000000…0015
0x1b6862…e19c
22 touches
55 conflicts
0x179acef0…e0ec
0xd32edf…ff58
21 touches
55 conflicts
0x00000000…0040
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…0052
0x1b6862…e19c
20 touches
45 conflicts
0x69d01970…c72c
0x1b6862…e19c
20 touches
45 conflicts
0xfab9e386…2463
0x1b6862…e19c
20 touches
45 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)
55 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity