pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,006,347
← previous block
next block →
recent activity
Analyzing
Block #92,006,347
13 transactions · 11 stateful · 2026-07-31 20:02:50 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,006,347
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
0x5a5d9a99
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#7
0x3f5c179b
#8
0x3f5c179b
#9
0x29eed2d3
#10
setData
#11
execOrders
#12
0x59558d29
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x167ca698…e836
0x34b655…2a6f
2 touches
0 conflicts
0x16d10a20…530f
0x34b655…2a6f
2 touches
0 conflicts
0x19bbf80f…0615
0x34b655…2a6f
2 touches
0 conflicts
0x1dd79365…4bab
0x34b655…2a6f
2 touches
0 conflicts
0x1eb410fd…591d
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
0x737acb7813…fafce8
Audit this contract →
← previous block
·
next block →
recent activity