pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#79,422,949
← previous block
next block →
recent activity
Analyzing
Block #79,422,949
12 transactions · 10 stateful · 2026-06-06 03:49:31 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#79,422,949
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 2
#3
updateDataFeedsValuesPartial
#4
setData
#5
0x57368ddf
#7
transfer
#8
approve
#9
0x3f5c179b
#10
0xc7e3ec2c
#11
0xc7e3ec2c
#2
0xab083028
#6
0x3f5c179b
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
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x28b01e5f…ced5
0x2880ab…7b43
2 touches
0 conflicts
0x28b01e5f…ced6
0x2880ab…7b43
2 touches
0 conflicts
0x749437cf…2fc0
0x2880ab…7b43
2 touches
0 conflicts
0x749437cf…2fc1
0x2880ab…7b43
2 touches
0 conflicts
0x9f3dfa2c…d6d5
0x2880ab…7b43
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: MarginAccount
1 conflict on slot
0x13a54fa2d3…a35ae3
Audit this contract →
← previous block
·
next block →
recent activity