← previous blocknext block →recent activity
Analyzing
Block #73,922,436
21 transactions · 19 stateful · 2026-05-11 16:19:10 UTC
Parallelism
71/100
Blocked
53%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,922,436 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w19w010w111w212w313w418w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x9d92359d…0ca7
0x34b655…2a6f
8 touches
6 conflicts
0xee230b20…5a0f
0x34b655…2a6f
8 touches
6 conflicts
0xac8e97a0…8426
0x34b655…2a6f
8 touches
6 conflicts
0x8a85cf3d…2868
0x34b655…2a6f
6 touches
3 conflicts
0x1319ae2c…7f9a
0x34b655…2a6f
6 touches
3 conflicts
0x4f483049…3cc7
0x34b655…2a6f
6 touches
3 conflicts
0xbc3d6b37…2215
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
10 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity