pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,789,003
← previous block
next block →
recent activity
Analyzing
Block #74,789,003
10 transactions · 8 stateful · 2026-05-15 16:39:05 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,789,003
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
#3
modifyLiquidities
#4
0x98717539
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x46636b…2470
#7
setData
#9
0x42dd8743
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x038aa895…2f47
0x34b655…2a6f
4 touches
1 conflict
0x388e001a…7e04
0x34b655…2a6f
4 touches
1 conflict
0xf853eb8e…4027
0x34b655…2a6f
4 touches
1 conflict
0x846f2172…fd54
0x0555e3…2b9c
2 touches
0 conflicts
0x95daa616…2e84
0x0555e3…2b9c
2 touches
0 conflicts
0x0344a613…5889
0x188d58…ea8e
2 touches
0 conflicts
0x09beabbc…065f
0x188d58…ea8e
2 touches
0 conflicts
0x2251d2a7…b5e8
0x188d58…ea8e
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
0x038aa89501…482f47
Audit this contract →
← previous block
·
next block →
recent activity