pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,293,878
20 transactions · 19 stateful · 2026-05-13 09:32:39 UTC
Parallelism
45/100
Blocked
53%
Avg conflicts / tx
2.4
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #74,293,878 · 20 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w27w38w49w510w611w712w818w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5de96bd3…c60c
0x34b655…2a6f
18 touches
36 conflicts
0xd0d1435f…56f7
0x34b655…2a6f
18 touches
36 conflicts
0xc6417de0…2191
0xc8689a…ee79
16 touches
28 conflicts
0x9be2b99a…a959
0x34b655…2a6f
14 touches
21 conflicts
0x5d70606a…1d53
0x34b655…2a6f
14 touches
21 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
14 touches
21 conflicts
0xa009aa7b…a5ba
0x34b655…2a6f
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: 0x34b6552d…112a6f
36 conflicts on slot 0x5de96bd34a…ecc60c
Audit this contract →
← previous block·next block →recent activity