pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,088,590
← previous block
next block →
recent activity
Analyzing
Block #91,088,590
10 transactions · 8 stateful · 2026-07-28 15:03:36 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,088,590
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execFwdPositionOps
· blocks 1
#3
0x29eed2d3
· blocks 1
#6
updateDataFeedsValuesPartial
#7
0x6a68c540
#8
execOrders
#9
0x59558d29
#4
0x29eed2d3
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5311f864…0984
0x754704…b603
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x10f6ad02…d262
0x34b655…2a6f
2 touches
0 conflicts
0x1a3e0d2e…4f3b
0x34b655…2a6f
2 touches
0 conflicts
0x1e3dc02f…b1bb
0x34b655…2a6f
2 touches
0 conflicts
0x30ae635d…5e67
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e65
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
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity