← previous blocknext block →recent activity
Analyzing
Block #102,648,731
28 transactions · 23 stateful · 2026-09-07 03:38:52 UTC
Parallelism
68/100
Blocked
57%
Avg conflicts / tx
1.68
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #102,648,731 · 28 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w48w59w610w617w720w821w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
18 touches
36 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
14 touches
21 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
14 touches
21 conflicts
0xaad6be10…0801
0x2a68ba…90c5
12 touches
15 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
10 touches
10 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0xca073497…3a50
0x065c9d…c394
5 touches
3 conflicts
0x78acc3ce…28cb
0x065c9d…c394
4 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
36 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity