← previous blocknext block →recent activity
Analyzing
Block #101,087,327
20 transactions · 20 stateful · 2026-09-01 16:15:57 UTC
Parallelism
80/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,087,327 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w06w110w113w215w116w217w319w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd52cdd17…928b
0x99c7a7…8bf0
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x5d4463c7…0c3e
0x754704…b603
4 touches
1 conflict
0x5f0647bd…59b9
0x754704…b603
4 touches
1 conflict
0xce62e150…1e09
0x754704…b603
4 touches
1 conflict
0xcf570cc1…b19c
0x99c7a7…8bf0
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity