pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,064,923
← previous block
next block →
recent activity
Analyzing
Block #91,064,923
10 transactions · 8 stateful · 2026-07-28 13:04:29 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
#91,064,923
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
execFwdPositionOps
#4
updateDataFeedsValuesPartial
#5
0x3f5c179b
· blocks 1
#7
0x6a68a955
#8
setData
#9
execOrders
#6
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x638748c3…4305
0x851145…3f07
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x17401558…520d
0x34b655…2a6f
2 touches
0 conflicts
0x2464f36f…724c
0x34b655…2a6f
2 touches
0 conflicts
0x598dd32b…eadd
0x34b655…2a6f
2 touches
0 conflicts
0x66d5e476…8a1f
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:
0x851145ea…9f3f07
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity