← previous blocknext block →recent activity
Analyzing
Block #102,051,569
20 transactions · 18 stateful · 2026-09-05 01:13:10 UTC
Parallelism
75/100
Blocked
61%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,051,569 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w28w39w010w111w212w417w218w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb838476…c1f1
0x065c9d…c394
8 touches
6 conflicts
0x2b498c69…bfd4
0x065c9d…c394
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
8 touches
6 conflicts
0x06e40499…165e
0x34ae4d…3fc5
8 touches
6 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
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
6 conflicts on slot 0xeb838476ae…acc1f1
Audit this contract →
← previous block·next block →recent activity