pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,221,240
← previous block
next block →
recent activity
Analyzing
Block #86,221,240
12 transactions · 9 stateful · 2026-07-07 15:41:29 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,221,240
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x6ad2e98b
· blocks 1
#3
execOrders
#4
execPerpOps
#5
execPerpOps
#6
aggregate3
#8
execFwdPositionOps
#9
updateDataFeedsValuesPartial
#10
0x6a4d1ea1
#11
setData
#7
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x934b15f1…b5a9
0x851145…3f07
4 touches
1 conflict
0xa0fe87a2…7da7
0x851145…3f07
3 touches
1 conflict
0xcabf9f66…dafd
0x851145…3f07
3 touches
1 conflict
0x31834267…6e2b
0x851145…3f07
3 touches
1 conflict
0x85a6f6b7…6d35
0x851145…3f07
3 touches
1 conflict
0x915c095e…c1e5
0x69df8a…6292
2 touches
0 conflicts
0xcfe06a18…b5b5
0x69df8a…6292
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:
0x851145ea…9f3f07
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity