← previous blocknext block →recent activity
Analyzing
Block #101,968,585
25 transactions · 23 stateful · 2026-09-04 18:12:35 UTC
Parallelism
88/100
Blocked
26%
Avg conflicts / tx
0.32
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,968,585 · 25 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
1w02w13w25w16w28w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6a8c250…737b
0x1b6862…e19c
6 touches
3 conflicts
0x7e81c352…1b26
0x34b655…2a6f
6 touches
3 conflicts
0x1d9867ad…6d9a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xeff6266a…dc1a
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
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 0xc6a8c25058…8d737b
Audit this contract →
← previous block·next block →recent activity