← previous blocknext block →recent activity
Analyzing
Block #97,528,312
20 transactions · 16 stateful · 2026-08-20 04:17:35 UTC
Parallelism
85/100
Blocked
31%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,528,312 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w09w112w216w017w118w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xe885cf9c…ff6f
0x065c9d…c394
4 touches
1 conflict
0x4d19b87e…1766
0x065c9d…c394
3 touches
1 conflict
0x40bb9136…b940
0x065c9d…c394
3 touches
1 conflict
0x3be4a49a…8357
0x065c9d…c394
3 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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity