← previous blocknext block →recent activity
Analyzing
Block #102,741,779
32 transactions · 23 stateful · 2026-09-07 11:27:01 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.44
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,741,779 · 32 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w111w213w015w116w318w019w126w427w530w031w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xd0fb8ecb…4aa6
0xd32edf…ff58
5 touches
3 conflicts
0x06e40499…165e
0x34ae4d…3fc5
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x1c0be074…2a3b
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity