← previous blocknext block →recent activity
Analyzing
Block #108,919,103
28 transactions · 26 stateful · 2026-09-29 02:36:30 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,919,103 · 28 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
1w02w13w24w35w47w08w116w019w020w324w426w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xd996735f…8733
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x5721fb7d…142f
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0056
0x1b6862…e19c
8 touches
6 conflicts
0x196dda99…dcf2
0x1b6862…e19c
8 touches
6 conflicts
0xd6c2779d…3c4e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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)
10 conflicts on slot 0x0000000000…000015
Audit this contract →
← previous block·next block →recent activity