← previous blocknext block →recent activity
Analyzing
Block #112,611,792
20 transactions · 18 stateful · 2026-10-12 00:28:44 UTC
Parallelism
70/100
Blocked
72%
Avg conflicts / tx
1.2
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #112,611,792 · 20 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
1w02w13w14w05w16w27w38w29w310w412w013w214w515w118w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x17a7f697…dcb8
0x1b6862…e19c
10 touches
10 conflicts
0xd6cafa62…35f9
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0058
0x1b6862…e19c
8 touches
6 conflicts
0x57d3b231…a413
0x1b6862…e19c
8 touches
6 conflicts
0xb8394f3d…8f29
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
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