← previous blocknext block →recent activity
Analyzing
Block #97,711,623
27 transactions · 21 stateful · 2026-08-20 19:52:04 UTC
Parallelism
81/100
Blocked
48%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,711,623 · 27 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
1w04w18w09w210w312w213w014w116w017w118w122w425w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36cbe85f…64c1
0x065c9d…c394
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x40ac662f…df77
0x34b655…2a6f
4 touches
1 conflict
0x422d5490…52d9
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x36cbe85fca…5c64c1
Audit this contract →
← previous block·next block →recent activity