pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,918,531
← previous block
next block →
recent activity
Analyzing
Block #90,918,531
9 transactions · 6 stateful · 2026-07-28 00:47:12 UTC
Parallelism
67
/100
Blocked
33
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,918,531
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execPerpOps
#2
withdraw
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#5
setData
#6
0xb4f550…c64a
#7
execOrders
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1a86a19b…b4e8
0x34b655…2a6f
2 touches
0 conflicts
0x355c1969…b199
0x34b655…2a6f
2 touches
0 conflicts
0x3ba37e3b…be50
0x34b655…2a6f
2 touches
0 conflicts
0x4295a3f8…97a1
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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
0xafb8e71eb0…ec9285
Audit this contract →
← previous block
·
next block →
recent activity