← previous blocknext block →recent activity
Analyzing
Block #102,040,884
15 transactions · 14 stateful · 2026-09-05 00:19:01 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,040,884 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0x22ba0fb5…7368
0x065c9d…c394
2 touches
0 conflicts
0x240fb084…d6d9
0x065c9d…c394
2 touches
0 conflicts
0x26049913…91af
0x065c9d…c394
2 touches
0 conflicts
0x368f0046…c4a2
0x065c9d…c394
2 touches
0 conflicts
0x3c50bab0…0aae
0x065c9d…c394
2 touches
0 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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity