← previous blocknext block →recent activity
Analyzing
Block #70,994,756
18 transactions · 15 stateful · 2026-04-28 02:58:00 UTC
Parallelism
78/100
Blocked
40%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #70,994,756 · 18 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
6w07w18w09w210w112w213w314w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xffe431af…8faa
0x131a2e…0da9
4 touches
2 conflicts
0x489cb750…7069
0x131a2e…0da9
4 touches
1 conflict
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
0x15d433dd…1693
0x754704…b603
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: MarginAccount
6 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity