pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,489,545
← previous block
next block →
recent activity
Analyzing
Block #86,489,545
13 transactions · 11 stateful · 2026-07-08 21:34:01 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,489,545
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
0xab083028
#3
execOrders
#4
execPerpOps
#5
execPerpOps
#6
0x5a5d9a99
#7
updateDataFeedsValuesPartial
#9
0x6a4ec2c1
#10
transfer
#11
setData
#12
execOrders
#8
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb5cfb85…c247
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xf5310ef7…485a
0x40c49f…2af0
4 touches
1 conflict
0x66e6480e…c384
0x40c49f…2af0
3 touches
1 conflict
0xae0efff8…db80
0x40c49f…2af0
3 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
2 touches
0 conflicts
0x9966da31…0d0f
0x34b655…2a6f
2 touches
0 conflicts
0xd16df6cd…5532
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:
0x40c49f17…d22af0
1 conflict on slot
0xcb5cfb85d7…15c247
Audit this contract →
← previous block
·
next block →
recent activity