← previous blocknext block →recent activity
Analyzing
Block #109,143,613
6 transactions · 6 stateful · 2026-09-29 21:30:00 UTC
Parallelism
50/100
Blocked
67%
Avg conflicts / tx
0.83
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #109,143,613 · 6 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a85a226…83bb
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x918bc6d9…5cf7
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0040
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0052
0x1b6862…e19c
4 touches
1 conflict
0x038d4614…c671
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
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)
3 conflicts on slot 0x0a85a2260d…5783bb
Audit this contract →
← previous block·next block →recent activity