← previous blocknext block →recent activity
Analyzing
Block #97,525,129
14 transactions · 14 stateful · 2026-08-20 04:01:35 UTC
Parallelism
86/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,525,129 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w07w18w111w012w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdbd4ac9c…07cc
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x107f84ba…8b0a
0x34b655…2a6f
4 touches
1 conflict
0x1b60b708…5b4b
0x2b46c0…1669
2 touches
0 conflicts
0x0ed52644…59b3
0x34b655…2a6f
2 touches
0 conflicts
0x1b53d138…3b57
0x34b655…2a6f
2 touches
0 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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity