← previous blocknext block →recent activity
Analyzing
Block #112,339,141
25 transactions · 22 stateful · 2026-10-11 01:36:57 UTC
Parallelism
68/100
Blocked
45%
Avg conflicts / tx
1.36
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #112,339,141 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w210w311w412w513w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0xc3483764…f297
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x0a58a6a7…d06d
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0052
0x1b6862…e19c
14 touches
21 conflicts
0x1d5648b1…c329
0x1b6862…e19c
14 touches
21 conflicts
0x9e9a67c9…e68d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 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)
28 conflicts on slot 0x0000000000…000015
Audit this contract →
← previous block·next block →recent activity