pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,774,495
← previous block
next block →
recent activity
Analyzing
Block #91,774,495
11 transactions · 10 stateful · 2026-07-31 00:36:27 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,774,495
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
#4
execFwdPositionOps
#5
execOrders
#6
execFwdPositionOps
#7
setData
#8
execOrders
· blocks 1
#10
0x59558d29
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36dddf94…3b71
0x34b655…2a6f
4 touches
1 conflict
0xd79e9cac…9f72
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x08de772c…8e84
0x2a68ba…90c5
2 touches
0 conflicts
0x0140fbd3…d957
0x34b655…2a6f
2 touches
0 conflicts
0x0bbc3da4…1d24
0x34b655…2a6f
2 touches
0 conflicts
0x27099c8c…d9d5
0x34b655…2a6f
2 touches
0 conflicts
0x310afe2c…83e1
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
0x36dddf94f0…573b71
Audit this contract →
← previous block
·
next block →
recent activity