pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,867,537
← previous block
next block →
recent activity
Analyzing
Block #90,867,537
9 transactions · 8 stateful · 2026-07-27 20:30:40 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,867,537
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#2
updatePrices
#4
execFwdPositionOps
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x59558d29
#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
0x48203298…65cb
0x34b655…2a6f
4 touches
1 conflict
0x7fafc50a…e3b0
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x05e1eba1…6491
0x34b655…2a6f
2 touches
0 conflicts
0x120a2553…7f53
0x34b655…2a6f
2 touches
0 conflicts
0x125c5f13…0368
0x34b655…2a6f
2 touches
0 conflicts
0x14b29ddb…0fd3
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
0x4820329863…2a65cb
Audit this contract →
← previous block
·
next block →
recent activity