← previous blocknext block →recent activity
Analyzing
Block #112,610,629
21 transactions · 18 stateful · 2026-10-12 00:22:53 UTC
Parallelism
81/100
Blocked
39%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,610,629 · 21 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
1w02w13w24w38w010w113w016w117w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x58e06bab…34d2
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x899899a9…87ae
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0040
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0058
0x1b6862…e19c
6 touches
3 conflicts
0x5d36d3c2…f78b
0x1b6862…e19c
6 touches
3 conflicts
0xdc7e2f53…8964
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 0x58e06babf4…8f34d2
Audit this contract →
← previous block·next block →recent activity