← previous blocknext block →recent activity
Analyzing
Block #108,020,865
24 transactions · 21 stateful · 2026-09-25 23:11:57 UTC
Parallelism
79/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,020,865 · 24 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
1w02w04w16w07w18w09w112w014w115w216w120w321w423w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb45d9d6…cb83
0x1b6862…e19c
6 touches
3 conflicts
0x4ea2b33b…7dbc
0x508254…98bd
6 touches
3 conflicts
0xd23e9468…049a
0x508254…98bd
6 touches
3 conflicts
0xe1c4d8e8…ffa8
0x508254…98bd
6 touches
3 conflicts
0x5f77d607…2c84
0x065c9d…c394
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0xccc3aedd…a57e
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
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 0xcb45d9d62a…b1cb83
Audit this contract →
← previous block·next block →recent activity