pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,280,150
← previous block
next block →
recent activity
Analyzing
Block #94,280,150
8 transactions · 8 stateful · 2026-08-08 18:47:21 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,280,150
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
execFwdPositionOps
· blocks 1
#4
0x3f5c179b
#5
updateDataFeedsValuesPartial
#6
setData
#7
execOrders
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9b077a8…e029
0x34b655…2a6f
4 touches
1 conflict
0x4cb81411…37f6
0x34b655…2a6f
4 touches
1 conflict
0x8ae3e2cf…d1a9
0x34b655…2a6f
4 touches
1 conflict
0x8f361903…8677
0x34b655…2a6f
4 touches
1 conflict
0x5502e1cc…3910
0x34b655…2a6f
4 touches
1 conflict
0x17abd0b1…f478
0x34b655…2a6f
2 touches
0 conflicts
0x1c097b81…0164
0x34b655…2a6f
2 touches
0 conflicts
0x3499d04b…5b2b
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
0xb9b077a82b…59e029
Audit this contract →
← previous block
·
next block →
recent activity