← previous blocknext block →recent activity
Analyzing
Block #112,484,373
30 transactions · 28 stateful · 2026-10-11 13:47:38 UTC
Parallelism
77/100
Blocked
54%
Avg conflicts / tx
1.37
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #112,484,373 · 30 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
1w02w13w06w07w19w010w111w212w315w416w518w121w522w223w324w425w528w629w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x394c3833…b4ab
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xed7bf906…bd10
0xd32edf…ff58
9 touches
10 conflicts
0x4aa45c58…bd37
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001c
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 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity