← previous blocknext block →recent activity
Analyzing
Block #108,472,447
24 transactions · 21 stateful · 2026-09-27 13:04:35 UTC
Parallelism
88/100
Blocked
48%
Avg conflicts / tx
0.54
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,472,447 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w19w010w111w012w115w016w117w218w122w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x1f8a126c…9aa5
0x1b6862…e19c
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xcf2d9b69…0cf7
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
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)
3 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity