pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,401,774
← previous block
next block →
recent activity
Analyzing
Block #93,401,774
9 transactions · 7 stateful · 2026-08-05 17:03:46 UTC
Parallelism
78
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,401,774
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0xb2d4797b
#3
execFwdPositionOps
· blocks 1
#4
batchCancelOrders
#6
setData
#7
0x59558d29
· blocks 1
#5
execFwdPositionOps
#8
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8c43f2ff…e857
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x096478d9…5940
0x34b655…2a6f
2 touches
0 conflicts
0x0a9408db…c24c
0x34b655…2a6f
2 touches
0 conflicts
0x1d048550…c6e1
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
0x8c43f2ff31…9fe857
Audit this contract →
← previous block
·
next block →
recent activity