← previous blocknext block →recent activity
Analyzing
Block #107,806,846
24 transactions · 20 stateful · 2026-09-25 05:14:41 UTC
Parallelism
88/100
Blocked
35%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #107,806,846 · 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
1w02w14w07w110w011w112w115w217w018w122w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c6
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x10e85b86…c20d
0x34b655…2a6f
4 touches
1 conflict
0x18e60108…c16d
0x34b655…2a6f
4 touches
1 conflict
0x1f84ce8a…5acc
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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)
1 conflict on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity