← previous blocknext block →recent activity
Analyzing
Block #72,398,961
64 transactions · 46 stateful · 2026-05-04 15:00:17 UTC
Parallelism
72/100
Blocked
74%
Avg conflicts / tx
2.44
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #72,398,961 · 64 txs across 18 waves · depth 18
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w16w17w08w110w211w113w314w418w249w150w351w452w553w255w356w457w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
28 touches
91 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xe54a1f6f…18f2
0x34b655…2a6f
12 touches
15 conflicts
0x3638e1ad…ec0e
0x34b655…2a6f
10 touches
10 conflicts
0xc6417de0…2191
0xc8689a…ee79
10 touches
10 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
10 touches
10 conflicts
0x12bc0d2c…1c12
0x34b655…2a6f
10 touches
10 conflicts
0x1319ae2c…7f9a
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
91 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity