← previous blocknext block →recent activity
Analyzing
Block #71,700,864
20 transactions · 19 stateful · 2026-05-01 09:24:05 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #71,700,864 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w17w18w29w110w011w112w113w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8ab5988…e091
0x065c9d…c394
7 touches
6 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
6 touches
3 conflicts
0x7c403af1…31b1
0x3bd359…433a
6 touches
3 conflicts
0x18aed20c…48f3
0x000000…012a
6 touches
3 conflicts
0x00000000…0002
0xd5b70d…615b
6 touches
3 conflicts
0x00000000…0004
0xd5b70d…615b
6 touches
3 conflicts
0x00000000…0000
0xd5b70d…615b
6 touches
3 conflicts
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
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
6 conflicts on slot 0xd8ab59882a…59e091
Audit this contract →
← previous block·next block →recent activity