← previous blocknext block →recent activity
Analyzing
Block #107,650,607
19 transactions · 19 stateful · 2026-09-24 16:06:57 UTC
Parallelism
74/100
Blocked
53%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,650,607 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w18w210w311w412w313w215w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x5cf4d55d…c588
0x34b655…2a6f
6 touches
3 conflicts
0x48a29a03…c438
0x1b6862…e19c
6 touches
3 conflicts
0x0fdeef7b…aeb1
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xfc5c21e0…91cb
0xd32edf…ff58
5 touches
3 conflicts
0x0221d4b2…fcf9
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