pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,290,520
← previous block
next block →
recent activity
Analyzing
Block #93,290,520
10 transactions · 9 stateful · 2026-08-05 07:44:24 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.3
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,290,520
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
0x5acec890
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#5
execFwdPositionOps
· blocks 1
#7
setData
#8
0x59558d29
#9
0xc7e3ec2c
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94de4d05…ad01
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x62030a81…91be
0x34b655…2a6f
4 touches
1 conflict
0xd30f9e74…d404
0x34b655…2a6f
4 touches
1 conflict
0x27b96981…ef48
0x34b655…2a6f
2 touches
0 conflicts
0x3750b746…5a9e
0x34b655…2a6f
2 touches
0 conflicts
0x6615cb1d…8a1e
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
0x94de4d05c1…d4ad01
Audit this contract →
← previous block
·
next block →
recent activity