pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,277,651
← previous block
next block →
recent activity
Analyzing
Block #90,277,651
11 transactions · 10 stateful · 2026-07-25 18:48:43 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
#90,277,651
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x5a5d9a99
#3
execFwdPositionOps
· blocks 1
#5
updateDataFeedsValuesPartial
#6
placeBet
#7
execOrders
#8
transfer
#9
setData
#10
execOrders
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbfa8a340…e305
0x34b655…2a6f
4 touches
1 conflict
0xe3684e08…c96a
0x34b655…2a6f
4 touches
1 conflict
0xeb3d5388…adb3
0x34b655…2a6f
3 touches
1 conflict
0x20f223d5…041b
0x34b655…2a6f
2 touches
0 conflicts
0x364026a6…1715
0x34b655…2a6f
2 touches
0 conflicts
0x48b13e5e…3c2a
0x34b655…2a6f
2 touches
0 conflicts
0x4ef82148…8a23
0x34b655…2a6f
2 touches
0 conflicts
0x4ef82148…8a24
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
0xbfa8a3404e…59e305
Audit this contract →
← previous block
·
next block →
recent activity