pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,302,375
← previous block
next block →
recent activity
Analyzing
Block #92,302,375
8 transactions · 7 stateful · 2026-08-01 20:51:40 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,302,375
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
#3
execFwdPositionOps
#4
0x57368ddf
#5
execFwdPositionOps
· blocks 1
#7
setData
#6
execOrders
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
0xe5a38e46…a68c
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x012d1c0c…0d83
0x34b655…2a6f
2 touches
0 conflicts
0x025fef2f…9738
0x34b655…2a6f
2 touches
0 conflicts
0x096f413f…d811
0x34b655…2a6f
2 touches
0 conflicts
0x0a16b979…4959
0x34b655…2a6f
2 touches
0 conflicts
0x0e727535…1759
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
0xe5a38e469a…0da68c
Audit this contract →
← previous block
·
next block →
recent activity