← previous blocknext block →recent activity
Analyzing
Block #71,283,782
8 transactions · 7 stateful · 2026-04-29 11:02:04 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,283,782 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xdd30f663…0016
0x065c9d…c394
4 touches
1 conflict
0xec20242b…ad8a
0x065c9d…c394
3 touches
1 conflict
0x21a4053c…c7e5
0x065c9d…c394
3 touches
1 conflict
0x236364d6…2d98
0x065c9d…c394
2 touches
0 conflicts
0x778710b5…08ff
0x065c9d…c394
2 touches
0 conflicts
0x9e5adf0e…51a5
0x065c9d…c394
2 touches
0 conflicts
0xf3d7a307…4d63
0x065c9d…c394
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