← previous blocknext block →recent activity
Analyzing
Block #99,210,498
23 transactions · 21 stateful · 2026-08-26 02:32:23 UTC
Parallelism
74/100
Blocked
29%
Avg conflicts / tx
0.52
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,210,498 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x348fda08…7e96
0x065c9d…c394
6 touches
3 conflicts
0xbb97db90…4c93
0xc8689a…ee79
6 touches
3 conflicts
0x8488f10f…9356
0x2b46c0…1669
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x45f562b2…9294
0x2b46c0…1669
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-MON/USDC
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity