← previous blocknext block →recent activity
Analyzing
Block #99,884,633
29 transactions · 28 stateful · 2026-08-28 11:19:04 UTC
Parallelism
69/100
Blocked
61%
Avg conflicts / tx
1.48
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #99,884,633 · 29 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w18w39w411w422w524w427w728w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xbb97db90…4c93
0xc8689a…ee79
10 touches
10 conflicts
0x9adc4798…acdd
0xd32edf…ff58
9 touches
10 conflicts
0x348fda08…7e96
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity