← previous blocknext block →recent activity
Analyzing
Block #73,036,581
34 transactions · 23 stateful · 2026-05-07 13:48:00 UTC
Parallelism
88/100
Blocked
39%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,036,581 · 34 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w07w111w112w017w118w019w120w221w323w127w233w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x222f86a7…a603
0xd32edf…ff58
7 touches
6 conflicts
0x8a35acfb…d1ac
0x8d66a4…3095
5 touches
3 conflicts
0x20ac0567…c954
0x34b655…2a6f
4 touches
1 conflict
0x2484cc15…5afc
0x34b655…2a6f
4 touches
1 conflict
0x25de453d…9573
0x34b655…2a6f
4 touches
1 conflict
0x318ac0bb…6b9c
0x34b655…2a6f
4 touches
1 conflict
0x3e639164…bc62
0x34b655…2a6f
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
6 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity