pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,845,174
← previous block
next block →
recent activity
Analyzing
Block #86,845,174
9 transactions · 6 stateful · 2026-07-10 13:12:47 UTC
Parallelism
67
/100
Blocked
33
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,845,174
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#2
updateDataFeedsValuesPartial
#5
setData
#6
0xb8024e59
#7
execOrders
#8
jMMeC
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03fb27fd…0c06
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x00958d6e…1d09
0x34b655…2a6f
2 touches
0 conflicts
0x00958d6e…1d0a
0x34b655…2a6f
2 touches
0 conflicts
0x5504c125…a597
0x34b655…2a6f
2 touches
0 conflicts
0x5fee1ba0…2520
0x34b655…2a6f
2 touches
0 conflicts
0x6d1dd8ad…024e
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
0x03fb27fddd…f00c06
Audit this contract →
← previous block
·
next block →
recent activity