← previous blocknext block →recent activity
Analyzing
Block #73,046,161
14 transactions · 13 stateful · 2026-05-07 14:51:47 UTC
Parallelism
43/100
Blocked
54%
Avg conflicts / tx
1.29
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,046,161 · 14 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
5w06w17w28w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x388e001a…7e04
0x34b655…2a6f
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1ab
0x8d66a4…3095
6 touches
3 conflicts
0x55b6a001…1e7a
0x34b655…2a6f
6 touches
3 conflicts
0x602ff3d4…3ebd
0x34b655…2a6f
6 touches
3 conflicts
0xf853eb8e…4027
0x34b655…2a6f
6 touches
3 conflicts
0x7cbd466f…1700
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 0x388e001a16…e57e04
Audit this contract →
← previous block·next block →recent activity