← previous blocknext block →recent activity
Analyzing
Block #102,345,014
33 transactions · 23 stateful · 2026-09-06 02:00:28 UTC
Parallelism
82/100
Blocked
43%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,345,014 · 33 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
1w03w15w06w17w210w214w016w317w421w324w425w527w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x929cea52…c72b
0x065c9d…c394
7 touches
6 conflicts
0x4e5afb3a…a338
0x3bd359…433a
6 touches
3 conflicts
0xff53b6b2…2f57
0x754704…b603
6 touches
3 conflicts
0x0fb999ce…da22
0x754704…b603
6 touches
3 conflicts
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
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