← previous blocknext block →recent activity
Analyzing
Block #71,342,787
10 transactions · 9 stateful · 2026-04-29 17:35:19 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,342,787 · 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
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xf1c07b7e…c5f7
0x1efe02…37d6
2 touches
0 conflicts
0xde38584a…ecb7
0x2a68ba…90c5
2 touches
0 conflicts
0x0175b7a6…1db9
0x7dfaf7…bf6a
2 touches
0 conflicts
0x0175b7a6…1dbb
0x7dfaf7…bf6a
2 touches
0 conflicts
0x3e4b8d9f…b8a7
0x7dfaf7…bf6a
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 0xfcb7b8b239…6bebb3
Audit this contract →
← previous block·next block →recent activity