pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,750,567
65 transactions · 44 stateful · 2026-05-15 12:21:41 UTC
Parallelism
82/100
Blocked
59%
Avg conflicts / tx
1.71
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #74,750,567 · 65 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w09w016w018w120w222w125w126w027w128w229w131w240w341w442w543w644w747w848w956w1057w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1d9d150…88db
0xd32edf…ff58
23 touches
66 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xea57afd0…4232
0x34b655…2a6f
14 touches
21 conflicts
0xea02471d…1542
0x34b655…2a6f
12 touches
15 conflicts
0x5ffc25fa…b119
0x34b655…2a6f
8 touches
6 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xf3d7a307…4d63
0x065c9d…c394
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: 0xd32edf66…9fff58
66 conflicts on slot 0xa1d9d150a3…8f88db
Audit this contract →
← previous block·next block →recent activity