pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,788,584
← previous block
next block →
recent activity
Analyzing
Block #90,788,584
12 transactions · 12 stateful · 2026-07-27 13:53:21 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,788,584
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
execute
#3
updatePrices
#4
0x5a5d9a99
· blocks 1
#5
updateDataFeedsValuesPartial
#7
0x3f5c179b
#8
execFwdPositionOps
#9
acceptTerms
#10
setData
#11
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf78ee7f…e7fd
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x24b6091e…d294
0x34b655…2a6f
2 touches
0 conflicts
0x2f4b1dc8…e9fa
0x34b655…2a6f
2 touches
0 conflicts
0x324ec4d3…f156
0x34b655…2a6f
2 touches
0 conflicts
0x34bcdc05…6689
0x34b655…2a6f
2 touches
0 conflicts
0x3e8569e7…04d7
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
0xbf78ee7fb5…b5e7fd
Audit this contract →
← previous block
·
next block →
recent activity