← previous blocknext block →recent activity
Analyzing
Block #99,812,309
32 transactions · 31 stateful · 2026-08-28 05:13:50 UTC
Parallelism
72/100
Blocked
71%
Avg conflicts / tx
1.81
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #99,812,309 · 32 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
1w02w13w24w05w36w47w58w69w111w512w615w122w723w225w826w327w430w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
8 touches
6 conflicts
0xbb97db90…4c93
0xc8689a…ee79
8 touches
6 conflicts
0x443a3e47…f4a4
0x065c9d…c394
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x06e40499…165e
0x2b46c0…1669
8 touches
6 conflicts
0xa605468c…1bfc
0x2b46c0…1669
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
21 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity