pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,663,404
← previous block
next block →
recent activity
Analyzing
Block #94,663,404
11 transactions · 10 stateful · 2026-08-10 03:04:27 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,663,404
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execOrders
#3
0xb2d4797b
#4
execFwdPositionOps
· blocks 1
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#8
setData
#9
execOrders
#10
0xc7e3ec2c
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5502e1cc…3910
0x34b655…2a6f
4 touches
1 conflict
0x5df99d31…3e25
0x34b655…2a6f
4 touches
1 conflict
0xceba0b65…6afe
0x34b655…2a6f
4 touches
1 conflict
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0018
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0028
0x1b6862…e19c
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
0x5502e1cc19…1a3910
Audit this contract →
← previous block
·
next block →
recent activity