pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#73,418,294
← previous block
next block →
recent activity
Analyzing
Block #73,418,294
12 transactions · 8 stateful · 2026-05-09 08:07:46 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,418,294
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xff401d8f
· blocks 1
#3
0x0f052239
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x62be7533
#8
0xc5a04723
#9
0x39435dac
#10
0x69feebca
#11
0xb4c62d…c075
#2
0x719d975a
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2a202ef3…c201
0x065c9d…c394
2 touches
0 conflicts
0x6f08361d…bda6
0x065c9d…c394
2 touches
0 conflicts
0x8757556e…fef3
0x065c9d…c394
2 touches
0 conflicts
0x8876d94c…8435
0x2a68ba…90c5
2 touches
0 conflicts
0x12530975…a089
0x3bd359…433a
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