← previous blocknext block →recent activity
Analyzing
Block #97,628,720
16 transactions · 15 stateful · 2026-08-20 12:45:44 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,628,720 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w16w07w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2044b9c…c271
0xa6afd3…d132
4 touches
1 conflict
0xbb55bcda…046e
0x34b655…2a6f
4 touches
1 conflict
0xcb99c025…30d8
0x34b655…2a6f
4 touches
1 conflict
0xef8649cd…8ebc
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0e1ceab4…7eda
0xa6afd3…d132
4 touches
1 conflict
0x6aa7a878…0103
0xa6afd3…d132
4 touches
1 conflict
0x8e06e67a…dfee
0x065c9d…c394
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-WETH/USDC
1 conflict on slot 0xc2044b9ce5…92c271
Audit this contract →
← previous block·next block →recent activity