pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#73,418,086
← previous block
next block →
recent activity
Analyzing
Block #73,418,086
10 transactions · 9 stateful · 2026-05-09 08:06:23 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,418,086
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x121eab2f
· blocks 1
#2
0x69feeb76
#3
removeLiquidity
#4
0x0c7abd22
#6
0x6df9e92b
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x39435dac
#5
0x62be7533
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe038916c…b1be
0x2a68ba…90c5
4 touches
1 conflict
0x12dea3b0…5459
0x065c9d…c394
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x6f08361d…bda6
0x065c9d…c394
2 touches
0 conflicts
0x809e88f8…1f76
0x065c9d…c394
2 touches
0 conflicts
0xf0ef078f…4528
0x065c9d…c394
2 touches
0 conflicts
0xf1e685ef…af49
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
0xe038916c87…fab1be
Audit this contract →
← previous block
·
next block →
recent activity