← previous blocknext block →recent activity
Analyzing
Block #110,321,837
19 transactions · 18 stateful · 2026-10-04 00:20:50 UTC
Parallelism
58/100
Blocked
50%
Avg conflicts / tx
1.58
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #110,321,837 · 19 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
1w05w16w27w38w49w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
16 touches
28 conflicts
0x6235638c…6437
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0xcb45d9d6…cb81
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0019
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0029
0x1b6862…e19c
16 touches
28 conflicts
0xacfa8b0c…cdd0
0xd32edf…ff58
15 touches
28 conflicts
0x3ec270a7…1d5f
0x34b655…2a6f
4 touches
1 conflict
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…000012
Audit this contract →
← previous block·next block →recent activity