pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,198,633
← previous block
next block →
recent activity
Analyzing
Block #94,198,633
12 transactions · 11 stateful · 2026-08-08 11:54:12 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,198,633
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
execOrders
#3
batchRequestPriceCallback
#4
multicall
#5
execFwdPositionOps
#6
execFwdPositionOps
· blocks 1
#8
0xed82b078
#9
0x6a77195b
#10
setData
· blocks 1
#7
execFwdPositionOps
#11
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x588380ee…0a5c
0x34b655…2a6f
4 touches
1 conflict
0x156552f7…c066
0x34b655…2a6f
4 touches
1 conflict
0x9f3dfa2c…d6d5
0x2880ab…7b43
2 touches
0 conflicts
0x9f3dfa2c…d6d6
0x2880ab…7b43
2 touches
0 conflicts
0xa367eff3…1905
0x2880ab…7b43
2 touches
0 conflicts
0xa367eff3…1906
0x2880ab…7b43
2 touches
0 conflicts
0x2c539d94…b63a
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:
0x33176be2…ede078
1 conflict on slot
0x09106a952c…111467
Audit this contract →
← previous block
·
next block →
recent activity