pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,010,089
← previous block
next block →
recent activity
Analyzing
Block #74,010,089
8 transactions · 8 stateful · 2026-05-12 02:05:18 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,010,089
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x1ffa3c9b
#3
0x39435dac
· blocks 1
#5
approve
#6
setData
#7
0x6a028b55
#4
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a469c7a…db41
0x34b655…2a6f
4 touches
1 conflict
0x5de96bd3…c60c
0x34b655…2a6f
4 touches
1 conflict
0xd49762c9…1359
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2158536d…e807
0x065c9d…c394
2 touches
0 conflicts
0x2c058970…7421
0x065c9d…c394
2 touches
0 conflicts
0x74db48d7…4eb7
0x065c9d…c394
2 touches
0 conflicts
0xd1abda48…767e
0x065c9d…c394
2 touches
0 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
1 conflict on slot
0x3a469c7ac1…29db41
Audit this contract →
← previous block
·
next block →
recent activity