← previous blocknext block →recent activity
Analyzing
Block #71,342,770
19 transactions · 13 stateful · 2026-04-29 17:35:12 UTC
Parallelism
68/100
Blocked
54%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #71,342,770 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w110w011w112w213w314w415w518w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0004
0x8d66a4…3095
10 touches
10 conflicts
0x8a35acfb…d1aa
0x8d66a4…3095
8 touches
6 conflicts
0xbd64801a…6689
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1ac
0x8d66a4…3095
6 touches
4 conflicts
0xe89e1a22…ce49
0x8d66a4…3095
6 touches
4 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x676f9f01…a8ac
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity