← previous blocknext block →recent activity
Analyzing
Block #71,446,573
7 transactions · 6 stateful · 2026-04-30 05:07:08 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,446,573 · 7 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
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf35ececb…9ac5
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xda1f4d7d…1a2d
0x065c9d…c394
3 touches
1 conflict
0x60dcfc4c…c326
0x065c9d…c394
2 touches
0 conflicts
0xa9525215…f25c
0x065c9d…c394
2 touches
0 conflicts
0xb22879bd…5d52
0x065c9d…c394
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
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 0xf35ececb3f…e39ac5
Audit this contract →
← previous block·next block →recent activity