pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,456,426
← previous block
next block →
recent activity
Analyzing
Block #93,456,426
13 transactions · 12 stateful · 2026-08-05 21:38:31 UTC
Parallelism
85
/100
Blocked
17
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,456,426
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
executeBatch
#6
0x94defb17
· blocks 1
#8
0xed82b078
#9
setData
#10
0x59558d29
· blocks 1
#12
0xc7e3ec2c
#7
0x94defb17
#11
0x59558d29
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
0x7643d03d…6082
0x968279…9342
4 touches
1 conflict
0x21343e01…dd55
0x968279…9342
4 touches
1 conflict
0x21343e01…dd56
0x968279…9342
4 touches
1 conflict
0x21343e01…dd59
0x968279…9342
4 touches
1 conflict
0x21343e01…dd5a
0x968279…9342
4 touches
1 conflict
0x21343e01…dd5c
0x968279…9342
4 touches
1 conflict
0x7643d03d…607f
0x968279…9342
4 touches
1 conflict
0x7643d03d…6080
0x968279…9342
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
0x7643d03dfe…306082
Audit this contract →
← previous block
·
next block →
recent activity