← previous blocknext block →recent activity
Analyzing
Block #71,330,162
10 transactions · 8 stateful · 2026-04-29 16:11:05 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,330,162 · 10 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
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76ed8777…1e5f
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x8af38771…36b6
0x34b655…2a6f
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x48611fa5…f6e8
0x065c9d…c394
2 touches
0 conflicts
0x9a5ca8f0…60cb
0x065c9d…c394
2 touches
0 conflicts
0xbf3f175b…c96b
0x065c9d…c394
2 touches
0 conflicts
0xd07c609a…d370
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: Perpl
1 conflict on slot 0x76ed8777f7…0c1e5f
Audit this contract →
← previous block·next block →recent activity