pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,859,946
86 transactions · 61 stateful · 2026-05-06 18:12:22 UTC
Parallelism
83/100
Blocked
72%
Avg conflicts / tx
1.93
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #72,859,946 · 86 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w18w09w010w115w018w220w222w324w431w539w140w357w258w459w560w662w763w865w770w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1049dc4e…a7c3
0xd32edf…ff58
15 touches
28 conflicts
0x7f189cf6…afab
0x065c9d…c394
14 touches
21 conflicts
0xbfca3cd0…5023
0x34b655…2a6f
14 touches
21 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
14 touches
21 conflicts
0x2ed00f98…da9f
0x34b655…2a6f
14 touches
21 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
14 touches
21 conflicts
0xafd59af5…5257
0xc8689a…ee79
14 touches
21 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: 0xd32edf66…9fff58
28 conflicts on slot 0x1049dc4ebd…9ca7c3
Audit this contract →
← previous block·next block →recent activity