pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,347,032
← previous block
next block →
recent activity
Analyzing
Block #92,347,032
10 transactions · 10 stateful · 2026-08-02 00:36:15 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,347,032
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
execFwdPositionOps
#3
execFwdPositionOps
#4
execOrders
· blocks 1
#6
0x6a6e9177
#7
setData
#8
execOrders
#9
0xc7e3ec2c
#5
execOrders
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
0xce06a0f7…efef
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x42b04648…21d1
0x34b655…2a6f
2 touches
0 conflicts
0x42b04648…21d2
0x34b655…2a6f
2 touches
0 conflicts
0x42b10c57…3ee7
0x34b655…2a6f
2 touches
0 conflicts
0x44276dc8…b281
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
0xce06a0f7c4…61efef
Audit this contract →
← previous block
·
next block →
recent activity