← previous blocknext block →recent activity
Analyzing
Block #108,517,384
15 transactions · 15 stateful · 2026-09-27 16:50:49 UTC
Parallelism
73/100
Blocked
40%
Avg conflicts / tx
0.93
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,517,384 · 15 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
2w03w14w05w06w19w110w213w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9dce5f78…29c5
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0002
0x125f12…a50b
8 touches
6 conflicts
0x3c98f31c…fddc
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0009
0x125f12…a50b
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)
6 conflicts on slot 0x9dce5f78d3…f529c5
Audit this contract →
← previous block·next block →recent activity