← previous blocknext block →recent activity
Analyzing
Block #102,061,021
16 transactions · 15 stateful · 2026-09-05 02:01:02 UTC
Parallelism
75/100
Blocked
53%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,061,021 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w17w29w210w111w212w314w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x839c0c71…bada
0x34b655…2a6f
6 touches
3 conflicts
0xa2eaf598…2cb0
0x34b655…2a6f
6 touches
3 conflicts
0xca544518…82c2
0x34b655…2a6f
6 touches
3 conflicts
0x26abdd19…639d
0x34b655…2a6f
4 touches
1 conflict
0x32e1d03e…68a7
0x34b655…2a6f
4 touches
1 conflict
0x3774a68c…11ff
0x34b655…2a6f
4 touches
1 conflict
0xda50c9d5…674e
0x34b655…2a6f
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