pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,916,874
← previous block
next block →
recent activity
Analyzing
Block #86,916,874
10 transactions · 8 stateful · 2026-07-10 21:12:09 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,916,874
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x957d4ba0
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x0c9bed1a
#5
execFwdPositionOps
#6
setData
#7
0x3f134c…c642
#8
0x1258dd…1339
#9
execOrders
#2
0x957d4ba0
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47d4745e…02bb
0x336ed4…c59c
4 touches
1 conflict
0x00000000…000a
0x90c374…be45
4 touches
1 conflict
0x00000000…000b
0x90c374…be45
4 touches
1 conflict
0x34443913…cbf3
0x336ed4…c59c
2 touches
0 conflicts
0x4a870d86…79ef
0x336ed4…c59c
2 touches
0 conflicts
0x93c58e4d…9b32
0x336ed4…c59c
2 touches
0 conflicts
0xc88f593e…5d93
0x336ed4…c59c
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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:
0x336ed437…cfc59c
1 conflict on slot
0x47d4745e02…9002bb
Audit this contract →
← previous block
·
next block →
recent activity