← previous blocknext block →recent activity
Analyzing
Block #100,919,486
12 transactions · 12 stateful · 2026-09-01 02:11:12 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,919,486 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5f77d607…2c84
0x065c9d…c394
4 touches
1 conflict
0x45f562b2…9294
0x34ae4d…3fc5
4 touches
1 conflict
0x8488f10f…9353
0x34ae4d…3fc5
4 touches
1 conflict
0x8488f10f…9354
0x34ae4d…3fc5
4 touches
1 conflict
0xa605468c…1bfc
0x34ae4d…3fc5
4 touches
1 conflict
0xc20bd100…8b0e
0x34ae4d…3fc5
4 touches
1 conflict
0xb686e6f5…f6d1
0xc8689a…ee79
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity