pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,064,920
← previous block
next block →
recent activity
Analyzing
Block #93,064,920
9 transactions · 9 stateful · 2026-08-04 12:48:49 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,064,920
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updatePriceFeedsIfNecessary
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
execOrders
· blocks 1
#7
cancelTournament
#8
setData
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x675d1afd…afef
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x4bc1abab…5874
0x34b655…2a6f
4 touches
1 conflict
0xcef1268c…3a53
0x34b655…2a6f
3 touches
1 conflict
0x0cfb5d79…7ccb
0x2880ab…7b43
2 touches
0 conflicts
0x0cfb5d79…7ccc
0x2880ab…7b43
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
0x675d1afde9…6dafef
Audit this contract →
← previous block
·
next block →
recent activity