pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,679,134
← previous block
next block →
recent activity
Analyzing
Block #90,679,134
7 transactions · 5 stateful · 2026-07-27 04:42:44 UTC
Parallelism
71
/100
Blocked
20
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,679,134
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 1
#4
forward
#5
execOrders
#6
execOrders
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4360b49f…140d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5fc5ada9…b06f
0x34b655…2a6f
4 touches
1 conflict
0x0eeb6471…7a41
0x34b655…2a6f
2 touches
0 conflicts
0x12348fc7…e86b
0x34b655…2a6f
2 touches
0 conflicts
0x19d0eecc…6863
0x34b655…2a6f
2 touches
0 conflicts
0x1fb504e7…ac6c
0x34b655…2a6f
2 touches
0 conflicts
0x2132931c…59f7
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
0x4360b49f2d…54140d
Audit this contract →
← previous block
·
next block →
recent activity