pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,575,222
← previous block
next block →
recent activity
Analyzing
Block #90,575,222
8 transactions · 8 stateful · 2026-07-26 19:59:58 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,575,222
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
placeBet
#4
updateDataFeedsValuesPartial
#5
0x6a6667b6
#6
setData
#7
execOrders
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x21303d7d…b483
0x34b655…2a6f
2 touches
0 conflicts
0x30479009…4c14
0x34b655…2a6f
2 touches
0 conflicts
0x33f54bd6…9ac3
0x34b655…2a6f
2 touches
0 conflicts
0x4253010a…4700
0x34b655…2a6f
2 touches
0 conflicts
0x8743e1ba…8331
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
0x66bdb4c268…a97ea6
Audit this contract →
← previous block
·
next block →
recent activity