← previous blocknext block →recent activity
Analyzing
Block #112,368,199
23 transactions · 22 stateful · 2026-10-11 04:03:08 UTC
Parallelism
83/100
Blocked
55%
Avg conflicts / tx
0.74
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,368,199 · 23 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
1w02w13w24w35w36w07w111w112w013w114w215w216w117w321w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17a7f697…dcb3
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xe93da786…19ad
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xdb40334f…e0bc
0xa6afd3…d132
6 touches
3 conflicts
0x57d3b231…a40e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0002
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 0x17a7f69751…9bdcb3
Audit this contract →
← previous block·next block →recent activity