pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,391,908
← previous block
next block →
recent activity
Analyzing
Block #92,391,908
12 transactions · 10 stateful · 2026-08-02 04:21:56 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,391,908
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xe33905c2
#2
0x5acec890
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execOrders
#5
0x6a6ec65c
#6
setData
#7
execOrders
#9
execOrders
#10
0x59558d29
#11
0xc7e3ec2c
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0xb6ea4726…5140
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x008e042e…0ba1
0x34b655…2a6f
2 touches
0 conflicts
0x0b2f55fa…9025
0x34b655…2a6f
2 touches
0 conflicts
0x18a8f68d…23c4
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x31734e80…921f
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
0x0f2d78b1bb…5e7363
Audit this contract →
← previous block
·
next block →
recent activity