← previous blocknext block →recent activity
Analyzing
Block #112,490,563
28 transactions · 26 stateful · 2026-10-11 14:18:47 UTC
Parallelism
79/100
Blocked
54%
Avg conflicts / tx
1.04
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #112,490,563 · 28 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
1w02w13w24w35w48w09w111w215w016w117w118w219w220w325w326w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x3af0dd8e…0025
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x6d48e4df…8436
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0055
0x1b6862…e19c
6 touches
3 conflicts
0x086626ee…2ad4
0x1b6862…e19c
6 touches
3 conflicts
0x5fd6ff96…b749
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
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)
10 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity