← previous blocknext block →recent activity
Analyzing
Block #100,852,455
104 transactions · 103 stateful · 2026-08-31 20:34:02 UTC
Parallelism
96/100
Blocked
7%
Avg conflicts / tx
0.12
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,852,455 · 104 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w07w110w011w012w1102w1103w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a85a226…83bd
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xd642305b…e8ba
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5de7f4e0…c7cd
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)
3 conflicts on slot 0x0a85a2260d…5783bd
Audit this contract →
← previous block·next block →recent activity