← previous blocknext block →recent activity
Analyzing
Block #73,924,032
12 transactions · 12 stateful · 2026-05-11 16:29:47 UTC
Parallelism
58/100
Blocked
58%
Avg conflicts / tx
1.25
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,924,032 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w27w29w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee230b20…5a0f
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x9d92359d…0ca7
0x34b655…2a6f
6 touches
3 conflicts
0x9d652ee8…83ca
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x5d70606a…1d53
0x34b655…2a6f
6 touches
3 conflicts
0x4f483049…3cc7
0x34b655…2a6f
6 touches
3 conflicts
0x578e7f66…1b56
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 0xee230b202a…c05a0f
Audit this contract →
← previous block·next block →recent activity