pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,363,868
← previous block
next block →
recent activity
Analyzing
Block #86,363,868
10 transactions · 8 stateful · 2026-07-08 07:33:47 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,363,868
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
#4
0x3f5c179b
#5
execFwdPositionOps
· blocks 1
#6
setData
#7
0xa091c3…1991
#8
execOrders
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac48f0d5…3ebf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x567bb003…113a
0x34b655…2a6f
4 touches
1 conflict
0x5dc93134…aaef
0x34b655…2a6f
4 touches
1 conflict
0x9fcbfbb7…ef34
0x34b655…2a6f
4 touches
1 conflict
0x9e04dfd7…f9eb
0x40c49f…2af0
2 touches
0 conflicts
0xb1f005e1…4696
0x40c49f…2af0
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
0xac48f0d5e5…2f3ebf
Audit this contract →
← previous block
·
next block →
recent activity