pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,284,614
← previous block
next block →
recent activity
Analyzing
Block #74,284,614
9 transactions · 7 stateful · 2026-05-13 08:30:56 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,284,614
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x6a043738
#3
approve
#4
forward
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x39435dac
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9d2cf20…a668
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0xfe3b9476…2e67
0x34b655…2a6f
4 touches
1 conflict
0x016a4471…69e6
0x065c9d…c394
2 touches
0 conflicts
0x07a7a2f2…754f
0x065c9d…c394
2 touches
0 conflicts
0x203d7a20…80cf
0x065c9d…c394
2 touches
0 conflicts
0x25e8f4c4…1e2e
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
0xb9d2cf2005…28a668
Audit this contract →
← previous block
·
next block →
recent activity