pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,466,649
← previous block
next block →
recent activity
Analyzing
Block #94,466,649
11 transactions · 10 stateful · 2026-08-09 10:34:48 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,466,649
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
#2
0x5acec890
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 1
#7
executeBatch
#8
0x6a785840
#9
setData
#10
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c702894…9f4c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x3ab86b5a…8290
0x34b655…2a6f
4 touches
1 conflict
0x01e7b865…6e6f
0x188d58…ea8e
2 touches
0 conflicts
0x201d7cf1…f7f2
0x34b655…2a6f
2 touches
0 conflicts
0x22866298…d604
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e66
0x34b655…2a6f
2 touches
0 conflicts
0x34a1ee7e…fb20
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
0x4c70289445…3e9f4c
Audit this contract →
← previous block
·
next block →
recent activity