pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,484,342
← previous block
next block →
recent activity
Analyzing
Block #92,484,342
10 transactions · 9 stateful · 2026-08-02 12:06:50 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,484,342
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
redeemDelegations
#3
0x7c51d6cf
#4
0x0f6795d9
· blocks 1
#6
0x6a6f3352
#7
setData
#8
0x36326531
#9
0x39435dac
#5
0x0f6795d9
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
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x9c1a0106…de12
0x34b655…2a6f
4 touches
1 conflict
0x152a7024…b61f
0x34b655…2a6f
2 touches
0 conflicts
0x015088a9…b96e
0x40c49f…2af0
2 touches
0 conflicts
0x595233b5…c4aa
0x754704…b603
2 touches
0 conflicts
0x91eb94de…b47b
0x754704…b603
2 touches
0 conflicts
0xa1087a5c…66c4
0x754704…b603
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
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity