← previous blocknext block →recent activity
Analyzing
Block #100,047,679
35 transactions · 29 stateful · 2026-08-29 01:00:23 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,047,679 · 35 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
1w02w13w26w37w48w09w010w114w015w016w119w020w125w128w529w231w633w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x443a3e47…f4a4
0x065c9d…c394
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0x17a7f697…dcb4
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
15 conflicts on slot 0x443a3e479f…3af4a4
Audit this contract →
← previous block·next block →recent activity