← previous blocknext block →recent activity
Analyzing
Block #71,343,941
9 transactions · 8 stateful · 2026-04-29 17:43:01 UTC
Parallelism
78/100
Blocked
25%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,343,941 · 9 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
1w03w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f1419c…c52b
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7b2cc1e1…1d31
0x065c9d…c394
3 touches
1 conflict
0x1c0ba91e…2650
0x065c9d…c394
3 touches
1 conflict
0xcbfe25a7…766a
0x065c9d…c394
2 touches
0 conflicts
0xd8f4edb5…4c71
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
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: Market-MON/USDC
1 conflict on slot 0xf2f1419c79…fdc52b
Audit this contract →
← previous block·next block →recent activity