← previous blocknext block →recent activity
Analyzing
Block #112,171,796
22 transactions · 21 stateful · 2026-10-10 11:35:01 UTC
Parallelism
68/100
Blocked
57%
Avg conflicts / tx
1.64
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #112,171,796 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w08w010w011w112w213w314w315w416w517w619w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a6cb118…4ca9
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x326a02b5…8dad
0x34b655…2a6f
10 touches
10 conflicts
0x9ea5f30d…06e6
0xd32edf…ff58
9 touches
10 conflicts
0xca2a5765…0396
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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)
10 conflicts on slot 0x0a6cb11882…264ca9
Audit this contract →
← previous block·next block →recent activity