← previous blocknext block →recent activity
Analyzing
Block #97,529,157
17 transactions · 13 stateful · 2026-08-20 04:21:50 UTC
Parallelism
76/100
Blocked
31%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,529,157 · 17 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
2w07w08w19w210w316w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19edfad7…b3c8
0x065c9d…c394
8 touches
6 conflicts
0x11258774…9892
0x2a68ba…90c5
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0019
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0029
0x1b6862…e19c
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
6 conflicts on slot 0x19edfad7cd…a5b3c8
Audit this contract →
← previous block·next block →recent activity