pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,221,501
← previous block
next block →
recent activity
Analyzing
Block #94,221,501
10 transactions · 10 stateful · 2026-08-08 13:49:57 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.3
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,221,501
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
updatePrices
#3
0x5acec890
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
· blocks 1
#8
setData
#9
0xc7e3ec2c
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5811d93…8c73
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x758a0dd5…0f46
0x34b655…2a6f
4 touches
1 conflict
0xd800e635…b1d7
0x34b655…2a6f
4 touches
1 conflict
0x22e2bbb6…2720
0x34b655…2a6f
4 touches
1 conflict
0xf4f9cac7…fd98
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x4b32d24f…0428
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
0xa5811d93b4…4d8c73
Audit this contract →
← previous block
·
next block →
recent activity