← previous blocknext block →recent activity
Analyzing
Block #70,955,770
8 transactions · 7 stateful · 2026-04-27 22:38:12 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #70,955,770 · 8 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
2w03w04w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbbee74c2…567a
0x131a2e…0da9
4 touches
1 conflict
0x4ab14837…e1b2
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xbbee74c2…567a
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3da11c10…aa48
0x065c9d…c394
2 touches
0 conflicts
0x6a08f30b…402a
0x065c9d…c394
2 touches
0 conflicts
0x00000000…003d
0x131a2e…0da9
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: Market-MON/AUSD
1 conflict on slot 0xbbee74c2e7…6e567a
Audit this contract →
← previous block·next block →recent activity