← previous blocknext block →recent activity
Analyzing
Block #73,921,211
72 transactions · 54 stateful · 2026-05-11 16:11:01 UTC
Parallelism
72/100
Blocked
78%
Avg conflicts / tx
3.61
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #73,921,211 · 72 txs across 20 waves · depth 20
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w217w145w446w547w648w751w352w456w571w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
28 touches
91 conflicts
0xee230b20…5a0f
0x34b655…2a6f
28 touches
91 conflicts
0x86948c34…bd5e
0x34b655…2a6f
22 touches
55 conflicts
0xbc3d6b37…2215
0x34b655…2a6f
18 touches
36 conflicts
0xac8e97a0…8426
0x34b655…2a6f
18 touches
36 conflicts
0x4f483049…3cc7
0x34b655…2a6f
18 touches
36 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
18 touches
36 conflicts
0x9be2b99a…a959
0x34b655…2a6f
18 touches
36 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
91 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity