← previous blocknext block →recent activity
Analyzing
Block #71,244,700
10 transactions · 8 stateful · 2026-04-29 06:41:57 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,244,700 · 10 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
4w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0xea22b050…a303
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3e6ca04b…b66a
0x065c9d…c394
4 touches
1 conflict
0x5b1130f8…fa36
0x065c9d…c394
2 touches
1 conflict
0x5b1130f8…fa37
0x065c9d…c394
2 touches
1 conflict
0xa2104d1a…d5f8
0x065c9d…c394
2 touches
1 conflict
0xa2104d1a…d5f9
0x065c9d…c394
2 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 Vault (KURU-VAULT)
1 conflict on slot 0x0000000000…000004
Audit this contract →
← previous block·next block →recent activity