← previous blocknext block →recent activity
Analyzing
Block #97,362,378
29 transactions · 28 stateful · 2026-08-19 13:59:05 UTC
Parallelism
83/100
Blocked
21%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,362,378 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w09w010w215w316w428w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe01158fd…f982
0x1b6862…e19c
6 touches
3 conflicts
0xc91d4275…1d7c
0x34b655…2a6f
6 touches
3 conflicts
0xfb31d278…9107
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 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)
3 conflicts on slot 0xe01158fdb6…86f982
Audit this contract →
← previous block·next block →recent activity