pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,629,510
← previous block
next block →
recent activity
Analyzing
Block #90,629,510
8 transactions · 7 stateful · 2026-07-27 00:33:05 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,629,510
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
#4
0x3f5c179b
#5
0x3f5c179b
#6
setData
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37732607…ba00
0x34b655…2a6f
4 touches
1 conflict
0x94ddea60…a24d
0x34b655…2a6f
4 touches
1 conflict
0x0b37bb75…df9c
0x34b655…2a6f
4 touches
1 conflict
0x26d1c221…4d2a
0x34b655…2a6f
4 touches
1 conflict
0xda3eb3c3…9d60
0x34b655…2a6f
4 touches
1 conflict
0x79d64635…8590
0x34b655…2a6f
2 touches
0 conflicts
0x81c3faf7…3806
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
0x37732607f0…f9ba00
Audit this contract →
← previous block
·
next block →
recent activity