pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#73,687,903
← previous block
next block →
recent activity
Analyzing
Block #73,687,903
11 transactions · 10 stateful · 2026-05-10 14:06:56 UTC
Parallelism
73
/100
Blocked
30
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,687,903
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 3
#5
0x39435dac
#6
0x5bf9264c
#7
updateDataFeedsValuesPartial
#8
updatePriceFeedsIfNecessary
#9
setData
#10
jMMeC
#2
0x0c7abd22
#3
0x1094dc9f
· blocks 1
#4
0xb264ae19
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe90b7bce…c2e0
0xfa32f9…f3f0
6 touches
3 conflicts
0x99f666e3…b2a2
0x3bd359…433a
6 touches
3 conflicts
0x9194f4a3…10b8
0x754704…b603
6 touches
3 conflicts
0x00000000…0000
0xfa32f9…f3f0
6 touches
3 conflicts
0x00000000…0001
0xfa32f9…f3f0
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x73912233…4586
0x1b6862…e19c
4 touches
1 conflict
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:
0xfa32f9ec…fef3f0
3 conflicts on slot
0xe90b7bceb6…a7c2e0
Audit this contract →
← previous block
·
next block →
recent activity