pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,286,836
← previous block
next block →
recent activity
Analyzing
Block #92,286,836
8 transactions · 7 stateful · 2026-08-01 19:33:31 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,286,836
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
#4
execFwdPositionOps
· blocks 1
#6
0x6a6e4a83
#7
setData
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x58e2fdcd…ec43
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad05
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad07
0x34b655…2a6f
4 touches
1 conflict
0x3eae31ad…600e
0x34b655…2a6f
3 touches
1 conflict
0xdaf4f143…58d4
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…003d
0x447d2e…e9f5
2 touches
0 conflicts
0x1dc0057c…ea83
0x447d2e…e9f5
2 touches
0 conflicts
0x28d19871…1737
0x447d2e…e9f5
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
0x58e2fdcd02…54ec43
Audit this contract →
← previous block
·
next block →
recent activity