← previous blocknext block →recent activity
Analyzing
Block #70,845,461
27 transactions · 26 stateful · 2026-04-27 10:23:42 UTC
Parallelism
63/100
Blocked
58%
Avg conflicts / tx
2.11
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #70,845,461 · 27 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w07w08w09w111w112w214w315w417w218w319w520w621w722w825w126w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
18 touches
36 conflicts
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x2a354a63…0515
0x065c9d…c394
10 touches
10 conflicts
0x00000000…003d
0x131a2e…0da9
8 touches
6 conflicts
0x2a354a63…0515
0x131a2e…0da9
6 touches
4 conflicts
0x4ab14837…e1b2
0x2a68ba…90c5
6 touches
3 conflicts
0x8e66da19…66b6
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0004
0xd0f8a6…badc
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: MarginAccount
36 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity