pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,409,607
← previous block
next block →
recent activity
Analyzing
Block #92,409,607
10 transactions · 10 stateful · 2026-08-02 05:50:56 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,409,607
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
0xab083028
· blocks 1
#4
0x5acec890
#5
0x5acec890
#6
execFwdPositionOps
#7
execFwdPositionOps
· blocks 1
#9
setData
#3
0xab083028
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa940f3a4…c5e8
0x34b655…2a6f
4 touches
1 conflict
0x48315f67…c1a6
0x34b655…2a6f
4 touches
1 conflict
0x53bda555…3810
0x34b655…2a6f
4 touches
1 conflict
0x65d63aa3…d144
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x8510add2…f5b0
0x34b655…2a6f
4 touches
1 conflict
0x9ad325f5…cc43
0x34b655…2a6f
4 touches
1 conflict
0x9fb28830…635e
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
0xa940f3a4da…a9c5e8
Audit this contract →
← previous block
·
next block →
recent activity