← previous blocknext block →recent activity
Analyzing
Block #71,045,666
22 transactions · 18 stateful · 2026-04-28 08:36:51 UTC
Parallelism
68/100
Blocked
33%
Avg conflicts / tx
0.45
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #71,045,666 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
9w010w111w214w315w416w017w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x131a2e…0da9
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x8553e4c7…1b0d
0xd32edf…ff58
5 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x4ab14837…e1b2
0x2a68ba…90c5
4 touches
1 conflict
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0x5c8c6ab6…dc36
0x131a2e…0da9
3 touches
1 conflict
0xa23619a7…40e4
0x3bd359…433a
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity