pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,855,584
← previous block
next block →
recent activity
Analyzing
Block #93,855,584
10 transactions · 8 stateful · 2026-08-07 07:05:10 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,855,584
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x033c27…b7d9
#2
0xeb282f7f
#3
0x5acec890
#4
0x5acec890
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#7
execFwdPositionOps
· blocks 1
#8
setData
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3791ab14…2611
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x8f23960c…3d52
0x1efe02…37d6
2 touches
0 conflicts
0xea63e6e2…1ee1
0x1efe02…37d6
2 touches
0 conflicts
0x0eac6378…36f4
0x34b655…2a6f
2 touches
0 conflicts
0x10a7d541…fc05
0x34b655…2a6f
2 touches
0 conflicts
0x1a889cb6…dee3
0xea1b8e…c5ec
2 touches
0 conflicts
0x6eff5416…605d
0xea1b8e…c5ec
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
0x3791ab1419…0a2611
Audit this contract →
← previous block
·
next block →
recent activity