← previous blocknext block →recent activity
Analyzing
Block #71,746,869
12 transactions · 12 stateful · 2026-05-01 14:30:33 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,746,869 · 12 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
2w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6459c3d4…b121
0x065c9d…c394
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc0da61d2…7809
0x065c9d…c394
3 touches
1 conflict
0x8fc1e77a…a9a0
0x065c9d…c394
3 touches
1 conflict
0x4d4d6f9b…04ff
0x065c9d…c394
3 touches
1 conflict
0xacbc0928…af9b
0x065c9d…c394
3 touches
1 conflict
0x1a4b4152…0a08
0x33663b…4897
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 0x6459c3d43a…c0b121
Audit this contract →
← previous block·next block →recent activity