pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,850,546
← previous block
next block →
recent activity
Analyzing
Block #94,850,546
10 transactions · 8 stateful · 2026-08-10 18:47:18 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,850,546
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execOrder
#3
execOrder
· blocks 2
#6
execFwdPositionOps
#7
0xed82b078
#8
setData
#9
execOrders
#4
execOrder
· blocks 1
#5
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa558e115…fc88
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x026f32d2…f016
0x34b655…2a6f
2 touches
0 conflicts
0x05527801…9c11
0x34b655…2a6f
2 touches
0 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x312c22e5…3920
0x34b655…2a6f
2 touches
0 conflicts
0x319a48e0…7b26
0x34b655…2a6f
2 touches
0 conflicts
0x37bef14c…a6d5
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
3 conflicts on slot
0xa558e11562…cafc88
Audit this contract →
← previous block
·
next block →
recent activity