← previous blocknext block →recent activity
Analyzing
Block #102,810,669
40 transactions · 30 stateful · 2026-09-07 17:16:44 UTC
Parallelism
82/100
Blocked
60%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,810,669 · 40 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w07w08w29w010w113w315w016w117w218w319w020w124w226w127w028w329w134w435w537w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xfbe161dd…757b
0x3bd359…433a
8 touches
6 conflicts
0x443a3e47…f4a4
0x065c9d…c394
8 touches
6 conflicts
0x646e1d9b…7619
0xd32edf…ff58
7 touches
6 conflicts
0xd93b8cdc…6a9a
0x3bd359…433a
6 touches
3 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x6518075e…2b17
0x2a68ba…90c5
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