← previous blocknext block →recent activity
Analyzing
Block #71,330,773
19 transactions · 17 stateful · 2026-04-29 16:15:11 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
0.95
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #71,330,773 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w28w09w111w114w015w116w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x1c913164…5c2e
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1ae
0x8d66a4…3095
6 touches
3 conflicts
0x468c69b1…af11
0x8d66a4…3095
6 touches
3 conflicts
0x9d651568…2c87
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x143dba04…1b98
0x8d66a4…3095
4 touches
1 conflict
0x1e451306…7993
0x8d66a4…3095
4 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: Perpl
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity