pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,490,528
← previous block
next block →
recent activity
Analyzing
Block #94,490,528
12 transactions · 7 stateful · 2026-08-09 12:34:57 UTC
Parallelism
83
/100
Blocked
14
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,490,528
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
execOrders
#4
execOrders
#5
execOrders
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOps
· blocks 1
#9
execFwdPositionOps
#10
setData
#11
execOrders
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74f95963…01a2
0x34b655…2a6f
4 touches
1 conflict
0x70eec2ed…f791
0x34b655…2a6f
4 touches
1 conflict
0xde6e326b…ead3
0x34b655…2a6f
4 touches
1 conflict
0x0140fbd3…d957
0x34b655…2a6f
2 touches
0 conflicts
0x03c76d4b…8294
0x34b655…2a6f
2 touches
0 conflicts
0x054afe69…16e8
0x34b655…2a6f
2 touches
0 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
2 touches
0 conflicts
0x0bbe8ee6…4ede
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
0x74f9596374…0201a2
Audit this contract →
← previous block
·
next block →
recent activity