pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#71,044,390
← previous block
next block →
recent activity
Analyzing
Block #71,044,390
11 transactions · 10 stateful · 2026-04-28 08:28:22 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,044,390
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
0x69f0701d
· blocks 1
#4
0x98717539
· blocks 1
#6
0x0c7abd22
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
setData
#5
0x69f0701d
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
5
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x1c913164…5c2e
0x34b655…2a6f
4 touches
1 conflict
0x629480fc…7d2f
0x34b655…2a6f
4 touches
1 conflict
0x8a85cf3d…2868
0x34b655…2a6f
4 touches
1 conflict
0xdf889704…8950
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…7212
0x34b655…2a6f
2 touches
0 conflicts
0x313f2565…5b00
0x34b655…2a6f
2 touches
0 conflicts
0x57de3828…3fbb
0x34b655…2a6f
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:
0x681e908b…e1ae09
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity