← previous blocknext block →recent activity
Analyzing
Block #108,603,415
25 transactions · 23 stateful · 2026-09-28 00:04:03 UTC
Parallelism
84/100
Blocked
43%
Avg conflicts / tx
0.72
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,603,415 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w111w012w114w215w016w117w218w119w321w122w224w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8725f80c…ff70
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xbf457bd3…e4c2
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xa1f5b205…49f1
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
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 0x8725f80cbc…47ff70
Audit this contract →
← previous block·next block →recent activity