← previous blocknext block →recent activity
Analyzing
Block #102,531,297
18 transactions · 16 stateful · 2026-09-06 17:44:31 UTC
Parallelism
89/100
Blocked
19%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,531,297 · 18 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
1w02w15w07w08w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x643fa4aa…a822
0x754704…b603
4 touches
1 conflict
0x73bb65fc…650d
0x754704…b603
4 touches
1 conflict
0xd1eae902…bfd4
0x754704…b603
4 touches
1 conflict
0x14b2b355…8ce5
0x99c7a7…8bf0
4 touches
1 conflict
0xc446711e…b7cb
0x99c7a7…8bf0
4 touches
1 conflict
0x89352ce3…768c
0xd42a27…01c7
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