← previous blocknext block →recent activity
Analyzing
Block #112,612,065
14 transactions · 13 stateful · 2026-10-12 00:30:06 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,612,065 · 14 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
1w02w13w24w39w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf58eca50…59fd
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xd1e62590…038f
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0040
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0058
0x1b6862…e19c
4 touches
1 conflict
0x73714323…0a7b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
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