← previous blocknext block →recent activity
Analyzing
Block #70,910,729
19 transactions · 17 stateful · 2026-04-27 17:38:21 UTC
Parallelism
58/100
Blocked
47%
Avg conflicts / tx
1.63
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #70,910,729 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w19w010w211w312w113w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
16 touches
28 conflicts
0x489cb750…7069
0x131a2e…0da9
6 touches
3 conflicts
0x00000000…003d
0x131a2e…0da9
6 touches
3 conflicts
0x24968e6d…0132
0x131a2e…0da9
4 touches
2 conflicts
0x4ab14837…e1b2
0x2a68ba…90c5
4 touches
1 conflict
0x4cb2b152…2e00
0x131a2e…0da9
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x24968e6d…0132
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: MarginAccount
28 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity