← previous blocknext block →recent activity
Analyzing
Block #102,468,427
16 transactions · 15 stateful · 2026-09-06 12:25:38 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,468,427 · 16 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
2w09w011w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x3a39ff76…fe0a
0x34b655…2a6f
2 touches
0 conflicts
0x53e08444…d671
0x34b655…2a6f
2 touches
0 conflicts
0x66d0c4a4…add3
0x34b655…2a6f
2 touches
0 conflicts
0x6c7c1a4b…5751
0x34b655…2a6f
2 touches
0 conflicts
0x6dc1811e…2588
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