pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,179,123
← previous block
next block →
recent activity
Analyzing
Block #85,179,123
8 transactions · 8 stateful · 2026-07-02 19:55:26 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,179,123
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
· blocks 1
#2
0x0f6795d9
#3
updateDataFeedsValuesPartial
#4
0x6a46c2a5
#5
setData
#7
0xc7e3ec2c
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x801058a8…5bc3
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x086db8fc…0024
0x34b655…2a6f
2 touches
0 conflicts
0x0dd6d5ef…ccf9
0x34b655…2a6f
2 touches
0 conflicts
0x1061311b…1141
0x34b655…2a6f
2 touches
0 conflicts
0x1175233a…64e7
0x34b655…2a6f
2 touches
0 conflicts
0x181732de…9796
0x34b655…2a6f
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
0x801058a816…5a5bc3
Audit this contract →
← previous block
·
next block →
recent activity