pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#80,314,798
← previous block
next block →
recent activity
Analyzing
Block #80,314,798
12 transactions · 9 stateful · 2026-06-10 07:07:33 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,314,798
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
batchUpdate
#2
batchUpdate
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
forward
#7
execFwdPositionOps
#8
0x6a290dad
#9
setData
#10
0x73ce98…7c37
#11
0xc7e3ec2c
#3
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa973fa68…f94d
0xa6afd3…d132
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x21898044…a071
0x065c9d…c394
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0xdbadf6b0…43b2
0x33176b…e078
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: Market-WETH/USDC
1 conflict on slot
0xa973fa687b…98f94d
Audit this contract →
← previous block
·
next block →
recent activity