pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,852,636
← previous block
next block →
recent activity
Analyzing
Block #94,852,636
15 transactions · 15 stateful · 2026-08-10 18:57:49 UTC
Parallelism
87
/100
Blocked
7
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,852,636
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
setPrice
#2
setPrice
#3
setPrice
#4
setPrice
#5
execOrders
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOps
· blocks 1
#8
execFwdPositionOps
#9
0x3f5c179b
#10
0xed82b078
#11
0x6a7a1fa4
#12
transfer
#13
setData
#14
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
14
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x097b4de6…ed0c
0x34b655…2a6f
2 touches
0 conflicts
0x0a0cecef…4ed0
0x34b655…2a6f
2 touches
0 conflicts
0x28ceceef…ecc2
0x34b655…2a6f
2 touches
0 conflicts
0x3b9bb58c…e73a
0x34b655…2a6f
2 touches
0 conflicts
0x4aaa2679…4c1d
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
0x4acbdbcf7f…d0a8c6
Audit this contract →
← previous block
·
next block →
recent activity