← previous blocknext block →recent activity
Analyzing
Block #73,037,128
31 transactions · 25 stateful · 2026-05-07 13:51:38 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
1.06
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,037,128 · 31 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w112w013w114w215w316w417w518w620w225w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0x8a35acfb…d1ab
0x8d66a4…3095
8 touches
6 conflicts
0x32ee90db…decc
0x34b655…2a6f
6 touches
3 conflicts
0x388e001a…7e04
0x34b655…2a6f
6 touches
3 conflicts
0x578e7f66…1b56
0x34b655…2a6f
6 touches
3 conflicts
0x61ad45b1…15ac
0x34b655…2a6f
6 touches
3 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
6 touches
3 conflicts
0x7b50a82b…f53d
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
21 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity