pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,892,170
← previous block
next block →
recent activity
Analyzing
Block #90,892,170
11 transactions · 11 stateful · 2026-07-27 22:34:34 UTC
Parallelism
73
/100
Blocked
18
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,892,170
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
execFwdPositionOps
#3
forward
#4
0xed82b078
#5
0x6a67dd72
#6
setData
#7
execOrders
· blocks 2
#10
execOrders
#8
execOrders
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xf8f1e808…a4fd
0x34b655…2a6f
4 touches
1 conflict
0x45ef9175…5ab2
0x34b655…2a6f
4 touches
1 conflict
0x13a8510e…2f17
0x34b655…2a6f
2 touches
0 conflicts
0x2460815d…df15
0x34b655…2a6f
2 touches
0 conflicts
0x24b6a024…9739
0x34b655…2a6f
2 touches
0 conflicts
0x2c66ecd1…f41d
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
3 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity