← previous blocknext block →recent activity
Analyzing
Block #71,696,410
11 transactions · 8 stateful · 2026-05-01 08:54:30 UTC
Parallelism
73/100
Blocked
25%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #71,696,410 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf888fc3d…f629
0x065c9d…c394
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x68851a97…aacb
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb6b7f011…a01b
0xd32edf…ff58
3 touches
1 conflict
0x1075c86e…f04b
0x065c9d…c394
3 touches
1 conflict
0x848f2c1d…e627
0x065c9d…c394
3 touches
1 conflict
0x885ee043…cc8d
0x065c9d…c394
3 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
1 conflict on slot 0xf888fc3ddb…4ef629
Audit this contract →
← previous block·next block →recent activity