← previous blocknext block →recent activity
Analyzing
Block #102,867,854
11 transactions · 9 stateful · 2026-09-07 22:04:33 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,867,854 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
2 touches
0 conflicts
0x517122b6…5d93
0x065c9d…c394
2 touches
0 conflicts
0xa7d04bdb…f6ee
0x065c9d…c394
2 touches
0 conflicts
0xcab63535…7e04
0x065c9d…c394
2 touches
0 conflicts
0xda96c4cb…dbe9
0x065c9d…c394
2 touches
0 conflicts
0x3bcddceb…78e9
0x34b655…2a6f
2 touches
0 conflicts
0x5efd7300…d8a5
0x34b655…2a6f
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity