pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#79,122,759
← previous block
next block →
recent activity
Analyzing
Block #79,122,759
12 transactions · 12 stateful · 2026-06-04 18:24:14 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#79,122,759
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 2
#3
updateDataFeedsValuesPartial
#4
0x6a21c345
#5
0x6df9e92b
#7
0x3f5c179b
#8
forward
#9
handleOps
#10
setData
#11
0xc7e3ec2c
#2
0xab083028
#6
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xffa7d0a4…b10a
0x40c49f…2af0
4 touches
1 conflict
0xef65bff3…7c9d
0x2a68ba…90c5
2 touches
0 conflicts
0x342fbbca…d443
0x40c49f…2af0
2 touches
0 conflicts
0x213ee207…a151
0x69df8a…6292
2 touches
0 conflicts
0x40970e69…da50
0x69df8a…6292
2 touches
0 conflicts
0x53e50026…6d8c
0x69df8a…6292
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity