pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,613,452
← previous block
next block →
recent activity
Analyzing
Block #80,613,452
15 transactions · 11 stateful · 2026-06-11 16:18:56 UTC
Parallelism
87
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,613,452
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
forward
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x57368ddf
#5
forward
#6
forward
· blocks 1
#7
forward
#9
forward
#10
setData
#11
0xd647e4…d06a
#12
0xfe2363…0523
#13
0x39435dac
#14
0xc7e3ec2c
#8
forward
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
0x00000000…000b
0x81bf4b…e191
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…000b
0x4e14b7…ea9f
2 touches
0 conflicts
0x00000000…000b
0x68ba3f…6e5e
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:
0x81bf4bbd…9fe191
1 conflict on slot
0x0000000000…00000b
Audit this contract →
← previous block
·
next block →
recent activity