← previous blocknext block →recent activity
Analyzing
Block #71,742,810
8 transactions · 7 stateful · 2026-05-01 14:03:27 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,742,810 · 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xeedb7e85…ec3b
0x065c9d…c394
4 touches
1 conflict
0x688f527e…4cf0
0x065c9d…c394
3 touches
1 conflict
0x710c2ffb…75ac
0x065c9d…c394
3 touches
1 conflict
0x9fd5971c…bbc7
0x065c9d…c394
3 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
2 touches
0 conflicts
0x508387de…c644
0x2a68ba…90c5
2 touches
0 conflicts
0xd74d5bed…5e7e
0x2a68ba…90c5
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/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity