pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,139,693
← previous block
next block →
recent activity
Analyzing
Block #85,139,693
13 transactions · 12 stateful · 2026-07-02 15:32:52 UTC
Parallelism
85
/100
Blocked
17
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,139,693
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xf93a2c3e
· blocks 1
#3
updatePrices
#4
execOrders
#5
updateDataFeedsValuesPartial
#6
0x3f5c179b
#7
0x3f5c179b
#8
forward
#9
0x6a46851c
#10
setData
#11
execOrders
· blocks 1
#2
0x19260710
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d6cb721…c88c
0x34b655…2a6f
4 touches
1 conflict
0x444c3ac5…2a12
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x9c214fd7…a680
0x754704…b603
4 touches
1 conflict
0xdefea50d…0ed9
0x754704…b603
4 touches
1 conflict
0xcd4a0041…2169
0x3bd359…433a
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x63e48b…53f2
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
0x1d6cb7216b…15c88c
Audit this contract →
← previous block
·
next block →
recent activity