← previous blocknext block →recent activity
Analyzing
Block #102,706,369
23 transactions · 20 stateful · 2026-09-07 08:28:51 UTC
Parallelism
78/100
Blocked
45%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,706,369 · 23 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
1w02w14w15w214w015w116w217w318w419w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
6 touches
3 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x46356904…5ead
0x34b655…2a6f
6 touches
3 conflicts
0x06e40499…165e
0x34ae4d…3fc5
4 touches
1 conflict
0x5f77d607…2c84
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity