← previous blocknext block →recent activity
Analyzing
Block #71,745,791
16 transactions · 11 stateful · 2026-05-01 14:23:21 UTC
Parallelism
88/100
Blocked
9%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,745,791 · 16 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
4w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3e79356a…e02b
0x065c9d…c394
4 touches
1 conflict
0xc998adb0…35d7
0x065c9d…c394
4 touches
1 conflict
0x738c5c6c…cb48
0x065c9d…c394
3 touches
1 conflict
0x1b04e8fe…ff1d
0x065c9d…c394
3 touches
1 conflict
0xf79a02d6…7c53
0x065c9d…c394
3 touches
1 conflict
0x7cc1f864…e517
0x065c9d…c394
2 touches
0 conflicts
0xc58819f4…029f
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