← previous blocknext block →recent activity
Analyzing
Block #97,910,148
7 transactions · 7 stateful · 2026-08-21 12:41:23 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,910,148 · 7 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x1b60b708…5b4b
0x2b46c0…1669
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x226c292d…54e6
0x34b655…2a6f
2 touches
0 conflicts
0x38fff049…6bfd
0x34b655…2a6f
2 touches
0 conflicts
0x45885570…ed97
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