← previous blocknext block →recent activity
Analyzing
Block #108,498,593
23 transactions · 23 stateful · 2026-09-27 15:16:13 UTC
Parallelism
57/100
Blocked
61%
Avg conflicts / tx
1.91
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #108,498,593 · 23 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w59w610w711w817w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
18 touches
36 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
18 touches
36 conflicts
0xcb45d9d6…cb84
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…001c
0x1b6862…e19c
18 touches
36 conflicts
0xeca2dba4…767a
0xd32edf…ff58
17 touches
36 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x125f12…a50b
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)
36 conflicts on slot 0x0000000000…000012
Audit this contract →
← previous block·next block →recent activity