← previous blocknext block →recent activity
Analyzing
Block #99,242,650
30 transactions · 25 stateful · 2026-08-26 05:14:10 UTC
Parallelism
77/100
Blocked
56%
Avg conflicts / tx
0.93
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,242,650 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w39w011w412w513w216w017w319w422w123w224w628w129w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xea49caf6…abf2
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xfe45073e…6315
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0xa366dc41…b2d8
0xa6afd3…d132
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-MON/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity