← previous blocknext block →recent activity
Analyzing
Block #73,671,839
25 transactions · 21 stateful · 2026-05-10 12:18:26 UTC
Parallelism
88/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,671,839 · 25 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w07w08w19w216w117w120w021w123w224w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2438038…5fa7
0x34b655…2a6f
6 touches
3 conflicts
0xb526de48…1e2d
0xd32edf…ff58
5 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
0xb91a6f59…722c
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
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
3 conflicts on slot 0xf2438038b6…475fa7
Audit this contract →
← previous block·next block →recent activity