← previous blocknext block →recent activity
Analyzing
Block #102,563,610
37 transactions · 26 stateful · 2026-09-06 20:28:21 UTC
Parallelism
84/100
Blocked
58%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,563,610 · 37 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
1w05w110w011w012w113w115w216w317w018w119w226w027w228w129w230w331w432w535w236w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x892daf6e…48d8
0x065c9d…c394
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x9b4f173c…94e6
0x34b655…2a6f
6 touches
3 conflicts
0x5f77d607…2c84
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xb0e974c4…b84d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity