← previous blocknext block →recent activity
Analyzing
Block #71,591,478
13 transactions · 12 stateful · 2026-04-30 21:16:04 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,591,478 · 13 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
3w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6e362194…b1a1
0x065c9d…c394
4 touches
1 conflict
0x2e872903…ad2f
0x065c9d…c394
4 touches
1 conflict
0x0b179f3b…2c23
0x065c9d…c394
3 touches
1 conflict
0xe6794dbf…356e
0x065c9d…c394
3 touches
1 conflict
0x95cb2fbe…ceb3
0x065c9d…c394
3 touches
1 conflict
0x048fd57f…83cd
0x065c9d…c394
3 touches
1 conflict
0x8c8cafd7…ed0d
0x57ea24…2cec
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