pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,981,800
← previous block
next block →
recent activity
Analyzing
Block #91,981,800
10 transactions · 7 stateful · 2026-07-31 17:59:23 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,981,800
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x0c7abd22
#3
updateDataFeedsValuesPartial
#4
0x5a5d9a99
#5
execFwdPositionOps
· blocks 1
#7
execOrders
#8
setData
#9
0x59558d29
#6
execFwdPositionOps
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
0xbdc80bf7…e947
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x0835f2d8…e06a
0x34b655…2a6f
2 touches
0 conflicts
0x0d2e1791…c1dd
0x34b655…2a6f
2 touches
0 conflicts
0x1205ebd6…dad6
0x34b655…2a6f
2 touches
0 conflicts
0x1cf304d7…6030
0x34b655…2a6f
2 touches
0 conflicts
0x2210c4e2…2ea9
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
0xbdc80bf733…aae947
Audit this contract →
← previous block
·
next block →
recent activity