pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,959,694
← previous block
next block →
recent activity
Analyzing
Block #85,959,694
8 transactions · 6 stateful · 2026-07-06 10:35:19 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,959,694
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
· blocks 1
#4
0x6a4b855f
#5
setData
#6
0x7efa0f…fb3b
#7
0xc7e3ec2c
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb43f54d…7439
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x72ec3615…68d4
0x34b655…2a6f
3 touches
1 conflict
0x433efdf9…4ab8
0x34b655…2a6f
2 touches
0 conflicts
0x63c900f4…2600
0x34b655…2a6f
2 touches
0 conflicts
0x652bc0f0…6faf
0x34b655…2a6f
2 touches
0 conflicts
0x698bb82a…286a
0x34b655…2a6f
2 touches
0 conflicts
0x6eac5a5d…1730
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
0xbb43f54d6c…5d7439
Audit this contract →
← previous block
·
next block →
recent activity