pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#78,942,702
← previous block
next block →
recent activity
Analyzing
Block #78,942,702
11 transactions · 7 stateful · 2026-06-03 22:23:28 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#78,942,702
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xeabbe9d8
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
approve
#8
setData
#9
0x6a20a9d8
#10
0xc7e3ec2c
#2
execute302
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52c63247…ce02
0x0a3323…0a3c
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x04ddf6…7f33
2 touches
0 conflicts
0x00000000…0002
0x04ddf6…7f33
2 touches
0 conflicts
0x00000000…0003
0x04ddf6…7f33
2 touches
0 conflicts
0x00000000…000a
0x04ddf6…7f33
2 touches
0 conflicts
0x35a2c1ad…f105
0x0a3323…0a3c
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:
0x0a332311…6e0a3c
1 conflict on slot
0x52c63247e1…bace02
Audit this contract →
← previous block
·
next block →
recent activity