pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,646,801
← previous block
next block →
recent activity
Analyzing
Block #85,646,801
8 transactions · 7 stateful · 2026-07-04 23:49:57 UTC
Parallelism
63
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,646,801
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 1
#3
setData
#6
0xc7e3ec2c
#7
0xc7e3ec2c
#4
execOrders
· blocks 1
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02e0881c…2ead
0x34b655…2a6f
4 touches
1 conflict
0x11431f9d…42c5
0x34b655…2a6f
4 touches
1 conflict
0x827c46c4…a83c
0x34b655…2a6f
4 touches
1 conflict
0xb9b4eff6…c3ef
0x34b655…2a6f
4 touches
1 conflict
0xca111140…2c7a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdc8d4ee0…def3
0x34b655…2a6f
4 touches
1 conflict
0xef703f6c…c5d7
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0x02e0881c38…e42ead
Audit this contract →
← previous block
·
next block →
recent activity