pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,780,151
← previous block
next block →
recent activity
Analyzing
Block #91,780,151
11 transactions · 9 stateful · 2026-07-31 01:04:55 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,780,151
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
0x3f5c179b
#3
0x3f5c179b
#5
batchUpdate
#6
0x57368ddf
#7
updateDataFeedsValuesPartial
#8
execOrders
#9
setData
#10
execOrders
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88e771e8…7d4a
0x34b655…2a6f
4 touches
1 conflict
0x74f95963…01a2
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0e3b59e9…d9d0
0x34b655…2a6f
2 touches
0 conflicts
0x159cff26…7665
0x34b655…2a6f
2 touches
0 conflicts
0x2029b74e…c206
0x34b655…2a6f
2 touches
0 conflicts
0x2133f86a…e924
0x34b655…2a6f
2 touches
0 conflicts
0x26cbf1bb…c456
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:
Perpl
1 conflict on slot
0x88e771e8ba…5c7d4a
Audit this contract →
← previous block
·
next block →
recent activity