← previous blocknext block →recent activity
Analyzing
Block #112,235,829
21 transactions · 19 stateful · 2026-10-10 16:57:10 UTC
Parallelism
71/100
Blocked
58%
Avg conflicts / tx
1.19
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #112,235,829 · 21 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
1w02w13w24w05w16w27w311w312w414w415w518w019w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda6b535e…6d6e
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x8f8586f3…4bc7
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0040
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0058
0x1b6862…e19c
8 touches
6 conflicts
0x5825da64…5612
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 0xda6b535e6c…386d6e
Audit this contract →
← previous block·next block →recent activity