pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#73,673,950
← previous block
next block →
recent activity
Analyzing
Block #73,673,950
15 transactions · 13 stateful · 2026-05-10 12:32:43 UTC
Parallelism
87
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,673,950
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x6a007b62
· blocks 1
#3
0xcf7468f4
#5
0x6a007b62
#6
execOrders
#7
0x98717539
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
deposit
#11
updatePosition
#12
0xd10227eb
#13
forward
#14
setData
#4
0x6a007b63
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00f245ce…1e10
0x34b655…2a6f
2 touches
0 conflicts
0x04183f8d…069e
0x34b655…2a6f
2 touches
0 conflicts
0x11ce4bb0…6129
0x34b655…2a6f
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x1fee64e8…d434
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