← previous blocknext block →recent activity
Analyzing
Block #73,751,939
28 transactions · 20 stateful · 2026-05-10 21:19:01 UTC
Parallelism
71/100
Blocked
75%
Avg conflicts / tx
1.32
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,751,939 · 28 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
1w02w13w24w36w414w015w116w219w120w522w523w624w725w326w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a2657f5…e008
0x34b655…2a6f
12 touches
15 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x8996e8c5…d01a
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
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 0x8a2657f5c3…4ce008
Audit this contract →
← previous block·next block →recent activity