← previous blocknext block →recent activity
Analyzing
Block #108,603,015
28 transactions · 23 stateful · 2026-09-28 00:02:02 UTC
Parallelism
82/100
Blocked
43%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,603,015 · 28 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
2w03w04w05w16w17w110w215w216w318w320w425w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0xcb45d9d6…cb86
0x1b6862…e19c
8 touches
6 conflicts
0xe27cc942…4c9c
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
6 touches
3 conflicts
0xb6fcbbb7…2b31
0x34b655…2a6f
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 0xd9f18d9a4a…7f141d
Audit this contract →
← previous block·next block →recent activity