← previous blocknext block →recent activity
Analyzing
Block #109,234,030
22 transactions · 18 stateful · 2026-09-30 05:05:17 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #109,234,030 · 22 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
1w02w13w24w35w46w57w613w417w018w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7322fb4a…635b
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x277ccab5…7f50
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0040
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0054
0x1b6862…e19c
10 touches
10 conflicts
0x0e64cf42…c995
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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)
21 conflicts on slot 0x7322fb4afc…ac635b
Audit this contract →
← previous block·next block →recent activity