pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,150,019
← previous block
next block →
recent activity
Analyzing
Block #93,150,019
11 transactions · 9 stateful · 2026-08-04 19:57:59 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,150,019
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xcbbdb31a
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execPerpOps
#5
execPerpOps
#6
0x5acec890
#7
execFwdPositionOps
· blocks 1
#10
setData
#8
execFwdPositionOps
· blocks 1
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0d70a98…d179
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xcd93b2d2…30e6
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x2d541549…9cce
0x34b655…2a6f
2 touches
0 conflicts
0xea02471d…1539
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…002e
0x59df86…2780
2 touches
0 conflicts
0x00000000…002f
0x59df86…2780
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
0xa0d70a98f2…c6d179
Audit this contract →
← previous block
·
next block →
recent activity