← previous blocknext block →recent activity
Analyzing
Block #73,036,824
20 transactions · 17 stateful · 2026-05-07 13:49:36 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,036,824 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w29w010w115w216w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x388e001a…7e04
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xf853eb8e…4027
0x34b655…2a6f
10 touches
10 conflicts
0x61ad45b1…15ac
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xd574ca…7ab1
6 touches
3 conflicts
0x9b0235a2…a1dc
0x34b655…2a6f
6 touches
3 conflicts
0x23951077…539b
0x34b655…2a6f
6 touches
3 conflicts
0x7b97d40a…09ed
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
15 conflicts on slot 0x388e001a16…e57e04
Audit this contract →
← previous block·next block →recent activity