pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,180,127
← previous block
next block →
recent activity
Analyzing
Block #85,180,127
11 transactions · 10 stateful · 2026-07-02 20:02:06 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,180,127
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swap
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
0xed82b078
#6
0x6a46c436
#7
setData
#8
execOrders
· blocks 1
#10
0xc7e3ec2c
#2
swap
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa164d951…1534
0xe1c8b7…3022
4 touches
1 conflict
0xbf6b0334…9b9f
0x53bc12…7777
4 touches
1 conflict
0xcfee13cc…8246
0x53bc12…7777
4 touches
1 conflict
0x7cf5136f…ba69
0x9f3832…4ae4
4 touches
1 conflict
0xc6874efb…7efd
0x9f3832…4ae4
4 touches
1 conflict
0xe502b892…2b46
0x9f3832…4ae4
4 touches
1 conflict
0xe502b892…2b47
0x9f3832…4ae4
4 touches
1 conflict
0x3487ef93…807f
0xe1c8b7…3022
4 touches
1 conflict
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:
0xe1c8b733…e33022
1 conflict on slot
0xa164d95170…fa1534
Audit this contract →
← previous block
·
next block →
recent activity