← previous blocknext block →recent activity
Analyzing
Block #97,536,718
26 transactions · 22 stateful · 2026-08-20 04:59:52 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,536,718 · 26 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
3w04w05w06w17w28w09w010w117w118w225w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x27a04273…27c5
0x065c9d…c394
4 touches
1 conflict
0x987f0301…a29d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0x3a921be0…779c
0x2a68ba…90c5
4 touches
1 conflict
0x88cf5bdb…49cf
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