← previous blocknext block →recent activity
Analyzing
Block #72,309,415
36 transactions · 29 stateful · 2026-05-04 05:03:42 UTC
Parallelism
75/100
Blocked
69%
Avg conflicts / tx
1.94
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #72,309,415 · 36 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w725w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b7bcac3…8fbf
0x34b655…2a6f
16 touches
28 conflicts
0xb40480e0…578a
0xd32edf…ff58
15 touches
28 conflicts
0xea02471d…1542
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xba5743c7…21c0
0x1b6862…e19c
10 touches
10 conflicts
0xf823e97f…2ee6
0x065c9d…c394
8 touches
6 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
28 conflicts on slot 0x7b7bcac3fe…968fbf
Audit this contract →
← previous block·next block →recent activity