pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,482,402
← previous block
next block →
recent activity
Analyzing
Block #73,482,402
11 transactions · 10 stateful · 2026-05-09 15:14:13 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,482,402
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x121eab2f
· blocks 2
#2
0x69ff4fbc
#3
updateDataFeedsValuesPartial
#4
0x5bf9264c
#5
0x5bf9264c
#6
forward
#7
forward
#10
setData
#8
0x5339c59f
· blocks 1
#9
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0xde83cfdc…8f9c
0x065c9d…c394
4 touches
1 conflict
0xf6a5aa8d…99ae
0x065c9d…c394
3 touches
1 conflict
0xbd6623ca…2ba7
0x065c9d…c394
3 touches
1 conflict
0x0b390c61…dc07
0x065c9d…c394
2 touches
0 conflicts
0x74773052…852d
0x065c9d…c394
2 touches
0 conflicts
0x96e0ce45…4ebd
0x065c9d…c394
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
1 conflict on slot
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity