pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,301,192
← previous block
next block →
recent activity
Analyzing
Block #86,301,192
11 transactions · 10 stateful · 2026-07-08 00:35:17 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
#86,301,192
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrders
#3
0x3f5c179b
· blocks 1
#5
execFwdPositionOps
· blocks 1
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
0x6a4d9bbd
#10
setData
#4
batchUpdate
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3747c64…4ab9
0x34b655…2a6f
4 touches
1 conflict
0x4755fafb…859b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x8d638197…aabc
0x065c9d…c394
2 touches
0 conflicts
0xaa58b1e1…4528
0x065c9d…c394
2 touches
0 conflicts
0xf3edeb65…5dd8
0x065c9d…c394
2 touches
0 conflicts
0x0a6f5e37…6c3c
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
0xc3747c6470…884ab9
Audit this contract →
← previous block
·
next block →
recent activity