← previous blocknext block →recent activity
Analyzing
Block #70,982,332
15 transactions · 11 stateful · 2026-04-28 01:35:15 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #70,982,332 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w09w110w012w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ab14837…e1b2
0x2a68ba…90c5
4 touches
1 conflict
0x4cb2b152…2e00
0x131a2e…0da9
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x394a210a…e69c
0xd32edf…ff58
3 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002e
0x1b6862…e19c
2 touches
0 conflicts
0xd5b10148…e637
0x1b6862…e19c
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
1 conflict on slot 0x4ab14837eb…ffe1b2
Audit this contract →
← previous block·next block →recent activity