pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,182,330
← previous block
next block →
recent activity
Analyzing
Block #84,182,330
12 transactions · 11 stateful · 2026-06-28 05:08:24 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,182,330
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xb264ae19
#3
0xab083028
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
0xed82b078
· blocks 1
#7
0xed82b078
#9
setData
#10
execOrders
#11
0xc7e3ec2c
#8
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9db7b4d…2957
0x40c49f…2af0
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x2c7e7448…9501
0x0000a8…8888
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0b16149e…7d4d
0x065c9d…c394
2 touches
0 conflicts
0x77bf5665…e0d8
0x065c9d…c394
2 touches
0 conflicts
0x8503eeca…a1f6
0x065c9d…c394
2 touches
0 conflicts
0xd76dc154…c593
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:
0x40c49f17…d22af0
1 conflict on slot
0xa9db7b4dd0…562957
Audit this contract →
← previous block
·
next block →
recent activity