← previous blocknext block →recent activity
Analyzing
Block #107,824,430
17 transactions · 17 stateful · 2026-09-25 06:43:11 UTC
Parallelism
71/100
Blocked
53%
Avg conflicts / tx
1.29
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,824,430 · 17 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
1w02w13w24w35w18w09w110w211w312w315w016w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe783dfa4…549a
0x1b6862…e19c
8 touches
6 conflicts
0xa7ba83b5…d0a8
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0xd0ed83fc…4952
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 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)
6 conflicts on slot 0xe783dfa4d2…18549a
Audit this contract →
← previous block·next block →recent activity