← previous blocknext block →recent activity
Analyzing
Block #97,537,540
32 transactions · 28 stateful · 2026-08-20 05:04:00 UTC
Parallelism
88/100
Blocked
43%
Avg conflicts / tx
0.66
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,537,540 · 32 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
1w02w17w09w010w111w212w013w117w119w020w124w225w226w328w029w230w331w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x59a84baf…4dfa
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x103de0…bb55
6 touches
3 conflicts
0x4681609f…6493
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
6 touches
3 conflicts
0x4423a307…9f43
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: Kuru Exchange: Market-MON/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity