pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#78,942,791
← previous block
next block →
recent activity
Analyzing
Block #78,942,791
9 transactions · 7 stateful · 2026-06-03 22:24:04 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#78,942,791
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xe3a3c9cc
#2
updateDataFeedsValuesPartial
#3
0x9e76c652
#4
forward
#5
setData
#6
0x39435dac
· blocks 1
#8
0xc7e3ec2c
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x15c9b5bf…f732
0x34b655…2a6f
4 touches
1 conflict
0xfbabb02d…af07
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0006
0x2ab50b…5c41
2 touches
0 conflicts
0x018dac45…e6f9
0x2ab50b…5c41
2 touches
0 conflicts
0x05b8ccbb…46bc
0x2ab50b…5c41
2 touches
0 conflicts
0x06d60e39…4ebd
0x2ab50b…5c41
2 touches
0 conflicts
0x0b660325…52be
0x2ab50b…5c41
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:
Perpl
1 conflict on slot
0x15c9b5bf08…57f732
Audit this contract →
← previous block
·
next block →
recent activity