pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,484,168
← previous block
next block →
recent activity
Analyzing
Block #94,484,168
11 transactions · 8 stateful · 2026-08-09 12:02:58 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,484,168
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execOrders
#3
execOrders
#4
execFwdPositionOps
#5
execFwdPositionOps
· blocks 1
#7
forward
#8
updateDataFeedsValuesPartial
#9
0x6a786cea
#10
setData
#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
0x5146ef12…80c6
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x109c2330…f629
0x34b655…2a6f
2 touches
0 conflicts
0x22866298…d604
0x34b655…2a6f
2 touches
0 conflicts
0x27099c8c…d9d5
0x34b655…2a6f
2 touches
0 conflicts
0x2b8c5b87…0cac
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e66
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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
0x5146ef1273…6d80c6
Audit this contract →
← previous block
·
next block →
recent activity