pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,290,518
← previous block
next block →
recent activity
Analyzing
Block #93,290,518
11 transactions · 11 stateful · 2026-08-05 07:44:24 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,290,518
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
forward
#3
updateDataFeedsValuesPartial
#4
executeBatch
#5
0x94defb17
· blocks 1
#8
execFwdPositionOps
#9
setData
#10
0xc7e3ec2c
#6
0x94defb17
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdcef0bf6…c831
0x968279…9342
4 touches
1 conflict
0x8da21d8d…cd46
0x968279…9342
4 touches
1 conflict
0x8da21d8d…cd49
0x968279…9342
4 touches
1 conflict
0x8da21d8d…cd4a
0x968279…9342
4 touches
1 conflict
0x8da21d8d…cd4c
0x968279…9342
4 touches
1 conflict
0xdcef0bf6…c82e
0x968279…9342
4 touches
1 conflict
0xdcef0bf6…c82f
0x968279…9342
4 touches
1 conflict
0x482471ad…122f
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:
0x96827978…f09342
1 conflict on slot
0xdcef0bf64c…99c831
Audit this contract →
← previous block
·
next block →
recent activity