pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#73,674,253
← previous block
next block →
recent activity
Analyzing
Block #73,674,253
11 transactions · 9 stateful · 2026-05-10 12:34:46 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,674,253
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
transfer
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
0x98717539
#5
batchUpdate
· blocks 2
#8
batchUpdate
#9
setData
#10
0xb99270…f017
#6
batchUpdate
· blocks 1
#7
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x0ac31945…2c72
0x065c9d…c394
4 touches
1 conflict
0x276d0e6f…8d9c
0x065c9d…c394
2 touches
0 conflicts
0x17cf4141…d6c1
0x34b655…2a6f
2 touches
0 conflicts
0x4089d428…b018
0x34b655…2a6f
2 touches
0 conflicts
0x4ee0b65a…6d40
0x34b655…2a6f
2 touches
0 conflicts
0x51087f5a…61f7
0x34b655…2a6f
2 touches
0 conflicts
0x60f7fbaf…bd58
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:
Kuru Exchange: MarginAccount
3 conflicts on slot
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity