← previous blocknext block →recent activity
Analyzing
Block #109,132,745
30 transactions · 26 stateful · 2026-09-29 20:35:08 UTC
Parallelism
37/100
Blocked
85%
Avg conflicts / tx
4.03
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #109,132,745 · 30 txs across 19 waves · depth 19
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w69w710w812w913w1014w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…0013
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…0015
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…0019
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…0029
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…0040
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…0052
0x1b6862…e19c
24 touches
66 conflicts
0x394c3833…b4a8
0x1b6862…e19c
24 touches
66 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)
66 conflicts on slot 0x0000000000…000012
Audit this contract →
← previous block·next block →recent activity