← previous blocknext block →recent activity
Analyzing
Block #108,655,438
21 transactions · 18 stateful · 2026-09-28 04:26:03 UTC
Parallelism
71/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,655,438 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w06w17w18w29w110w311w412w513w218w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0018
0x1b6862…e19c
12 touches
15 conflicts
0xcb45d9d6…cb80
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x2e427a64…b6e7
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x60a536a6…ef7a
0x34b655…2a6f
4 touches
1 conflict
0x6ca15e14…7be8
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)
15 conflicts on slot 0x0000000000…000012
Audit this contract →
← previous block·next block →recent activity