← previous blocknext block →recent activity
Analyzing
Block #112,368,205
20 transactions · 19 stateful · 2026-10-11 04:03:10 UTC
Parallelism
80/100
Blocked
37%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,368,205 · 20 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
1w02w13w24w313w014w115w016w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69017fce…85bd
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x5bba9657…5048
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0053
0x1b6862…e19c
6 touches
3 conflicts
0x0a9870c4…8643
0x1b6862…e19c
6 touches
3 conflicts
0x92837c1a…7af8
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)
6 conflicts on slot 0x69017fce76…df85bd
Audit this contract →
← previous block·next block →recent activity