← previous blocknext block →recent activity
Analyzing
Block #112,612,425
29 transactions · 27 stateful · 2026-10-12 00:31:55 UTC
Parallelism
83/100
Blocked
30%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,612,425 · 29 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
1w02w13w24w310w012w213w114w215w319w023w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf58eca50…59fd
0x1b6862…e19c
8 touches
6 conflicts
0xccebf5c5…8758
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x1dcbb562…0022
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0040
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0058
0x1b6862…e19c
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 0xf58eca505b…9a59fd
Audit this contract →
← previous block·next block →recent activity