pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,378,132
← previous block
next block →
recent activity
Analyzing
Block #73,378,132
9 transactions · 7 stateful · 2026-05-09 03:40:21 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,378,132
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
setData
#3
0x39abec6b
#4
0xed82b078
· blocks 1
#6
0xed82b078
#7
0x69fead1d
#8
0xeffdedb0
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0x01a173b5…cb5c
0x2ab50b…5c41
2 touches
0 conflicts
0x01ea5a68…e607
0x2ab50b…5c41
2 touches
0 conflicts
0x0230870e…327e
0x2ab50b…5c41
2 touches
0 conflicts
0x080c1dbe…ba16
0x2ab50b…5c41
2 touches
0 conflicts
0x0845b1ad…7d11
0x2ab50b…5c41
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
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity