← previous blocknext block →recent activity
Analyzing
Block #112,485,268
19 transactions · 18 stateful · 2026-10-11 13:52:08 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #112,485,268 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w08w113w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x4d42f16e…a6ca
0x1b6862…e19c
12 touches
15 conflicts
0xcbb0cc98…cc20
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0055
0x1b6862…e19c
10 touches
10 conflicts
0x4d75d4b3…b811
0x1b6862…e19c
10 touches
10 conflicts
0x6968bb7b…41c5
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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)
15 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity