← previous blocknext block →recent activity
Analyzing
Block #98,023,434
43 transactions · 24 stateful · 2026-08-21 22:16:06 UTC
Parallelism
88/100
Blocked
50%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,023,434 · 43 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w19w218w322w023w024w127w230w334w035w438w139w240w341w442w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xc26c0c87…c857
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…0002
0xbb3f3c…e046
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x10abefc9…c9bc
0x2b46c0…1669
6 touches
3 conflicts
0x5778d110…d2e6
0xc8689a…ee79
6 touches
3 conflicts
0x40970e69…da50
0x2b46c0…1669
6 touches
3 conflicts
0x10d80fee…dbda
0x2b46c0…1669
6 touches
3 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-WETH/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity