← previous blocknext block →recent activity
Analyzing
Block #73,377,320
22 transactions · 20 stateful · 2026-05-09 03:34:57 UTC
Parallelism
64/100
Blocked
55%
Avg conflicts / tx
1.68
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,377,320 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w29w310w411w519w520w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c55258f…02df
0x34b655…2a6f
14 touches
21 conflicts
0xf853eb8e…4027
0x34b655…2a6f
14 touches
21 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
12 touches
15 conflicts
0x908d4442…2c4b
0x34b655…2a6f
12 touches
15 conflicts
0xa91c899f…6ee3
0x34b655…2a6f
12 touches
15 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0x57de3828…3fbb
0x34b655…2a6f
10 touches
10 conflicts
0xedb848fe…6534
0x34b655…2a6f
10 touches
10 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 0x0c55258fd5…fa02df
Audit this contract →
← previous block·next block →recent activity