← previous blocknext block →recent activity
Analyzing
Block #102,446,821
30 transactions · 27 stateful · 2026-09-06 10:36:03 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.27
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,446,821 · 30 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
2w05w18w013w114w116w227w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb83
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x686f9d2b…dbab
0xd32edf…ff58
5 touches
3 conflicts
0x982ba7f1…e834
0x11ed3b…2c96
4 touches
1 conflict
0xb7143610…adc4
0x3bd359…433a
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