pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#80,482,093
← previous block
next block →
recent activity
Analyzing
Block #80,482,093
15 transactions · 14 stateful · 2026-06-11 01:42:14 UTC
Parallelism
87
/100
Blocked
7
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,482,093
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
batchCancelOrders
#2
0x1a945f9c
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
aggregate3
#6
0x0c7abd22
#7
0x57368ddf
#8
0x3f5c179b
#9
forward
#10
0xe9316489
· blocks 1
#12
setData
#13
execOrders
#14
0xc7e3ec2c
#11
0xe9316489
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38937ad6…57d8
0x96b79e…d00a
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x21898044…a071
0x065c9d…c394
2 touches
0 conflicts
0x9a4736a3…b83b
0x065c9d…c394
2 touches
0 conflicts
0x207e7985…b608
0x1efe02…37d6
2 touches
0 conflicts
0x00000000…0099
0xaa3145…feec
2 touches
0 conflicts
0x7c64e716…6111
0xaa3145…feec
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:
0x96b79ef4…d2d00a
1 conflict on slot
0x38937ad63f…4557d8
Audit this contract →
← previous block
·
next block →
recent activity