pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,499,909
← previous block
next block →
recent activity
Analyzing
Block #86,499,909
11 transactions · 7 stateful · 2026-07-08 22:43:09 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,499,909
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execOrders
#3
execFwdPositionOps
#4
0x0c72758b
· blocks 1
#6
setData
#7
0xdbe258…f257
#8
0xa0d42d…c84d
#9
0xbf428d…069a
#10
execOrders
#5
0x0c72758b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0014
0x2f55a2…8375
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0fe52b98…9d90
0x34b655…2a6f
2 touches
0 conflicts
0x41bc570b…8315
0x34b655…2a6f
2 touches
0 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
2 touches
0 conflicts
0x50077087…ca34
0x34b655…2a6f
2 touches
0 conflicts
0x542b5bb7…2e0f
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:
0x2f55a2e1…f48375
1 conflict on slot
0x0000000000…000014
Audit this contract →
← previous block
·
next block →
recent activity