pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,454,895
← previous block
next block →
recent activity
Analyzing
Block #93,454,895
9 transactions · 8 stateful · 2026-08-05 21:30:50 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,454,895
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x5acec890
· blocks 1
#3
execFwdPositionOps
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x59558d29
#8
0xc7e3ec2c
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb91a6f59…722c
0x34b655…2a6f
4 touches
1 conflict
0xe3f2706b…d3ec
0x34b655…2a6f
4 touches
1 conflict
0xe9a321bc…88d5
0x34b655…2a6f
4 touches
1 conflict
0x05e1eba1…6491
0x34b655…2a6f
2 touches
0 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
2 touches
0 conflicts
0x4164abbf…e433
0x34b655…2a6f
2 touches
0 conflicts
0x4dfee17d…bb5e
0x34b655…2a6f
2 touches
0 conflicts
0x57e04406…a617
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
0xb91a6f59b9…c8722c
Audit this contract →
← previous block
·
next block →
recent activity