← previous blocknext block →recent activity
Analyzing
Block #70,892,639
11 transactions · 9 stateful · 2026-04-27 15:37:52 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #70,892,639 · 11 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
1w02w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36ecae44…6d6f
0x065c9d…c394
4 touches
1 conflict
0x8d7fce09…75cd
0x065c9d…c394
4 touches
1 conflict
0xbfab69ab…9c69
0x065c9d…c394
4 touches
1 conflict
0xc1ec49b3…8739
0x065c9d…c394
4 touches
1 conflict
0xe7ee6605…efd8
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xb857c1…9be1
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x00000000…003d
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
1 conflict on slot 0x36ecae4413…146d6f
Audit this contract →
← previous block·next block →recent activity