pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,359,623
← previous block
next block →
recent activity
Analyzing
Block #92,359,623
10 transactions · 10 stateful · 2026-08-02 01:39:34 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,359,623
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x0c7abd22
#3
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#6
0x6a6ea04e
#7
setData
#8
updatePrices
#9
0x59558d29
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8369eecf…1193
0x34b655…2a6f
4 touches
1 conflict
0xadec4d4d…eac8
0x34b655…2a6f
4 touches
1 conflict
0xb3832c92…d9d6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xeb272cf8…c8e3
0x34b655…2a6f
4 touches
1 conflict
0xf51ec09c…b4a9
0x34b655…2a6f
4 touches
1 conflict
0x00958d6e…1d09
0x34b655…2a6f
4 touches
1 conflict
0x00958d6e…1d0a
0x34b655…2a6f
4 touches
1 conflict
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
0x8369eecf49…021193
Audit this contract →
← previous block
·
next block →
recent activity