← previous blocknext block →recent activity
Analyzing
Block #97,563,422
16 transactions · 15 stateful · 2026-08-20 07:15:31 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,563,422 · 16 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
0w04w05w06w17w08w19w215w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf72df3d3…879b
0x065c9d…c394
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x0778475b…bd75
0x2a68ba…90c5
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
4 touches
1 conflict
0xda1f3e2c…b73d
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x7aa91b8f…d070
0x2b46c0…1669
2 touches
0 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
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
3 conflicts on slot 0xf72df3d3c4…c6879b
Audit this contract →
← previous block·next block →recent activity