pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,705,637
← previous block
next block →
recent activity
Analyzing
Block #90,705,637
10 transactions · 7 stateful · 2026-07-27 06:56:03 UTC
Parallelism
80
/100
Blocked
29
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,705,637
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execFwdPositionOps
· blocks 2
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
execFwdPositionOps
#7
batchUpdate
#9
setData
#3
execFwdPositionOps
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23769ebc…c8ed
0x34b655…2a6f
4 touches
1 conflict
0x4360b49f…140d
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810d
0x34b655…2a6f
4 touches
1 conflict
0xa10c3338…3d15
0x34b655…2a6f
4 touches
1 conflict
0xa5f761f5…e897
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xed4cf5a9…f734
0x34b655…2a6f
4 touches
1 conflict
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
0x23769ebc9a…0ec8ed
Audit this contract →
← previous block
·
next block →
recent activity