pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,222,889
← previous block
next block →
recent activity
Analyzing
Block #92,222,889
10 transactions · 9 stateful · 2026-08-01 14:11:53 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,222,889
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa1ca97…725d
#2
execOrders
· blocks 1
#4
execFwdPositionOps
· blocks 1
#6
0x3f5c179b
#7
execOrders
#8
0x6a6dff21
#9
setData
#3
execFwdPositionOps
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5a8ffca…8de2
0x34b655…2a6f
4 touches
1 conflict
0xa457c06e…2f06
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x05b22769…44af
0x34b655…2a6f
2 touches
0 conflicts
0x05f9e9c2…54e9
0x34b655…2a6f
2 touches
0 conflicts
0x1de49243…4aa3
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad05
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
0xa5a8ffca31…818de2
Audit this contract →
← previous block
·
next block →
recent activity