pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,429,165
← previous block
next block →
recent activity
Analyzing
Block #90,429,165
9 transactions · 9 stateful · 2026-07-26 07:43:46 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,429,165
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x62be7533
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
#4
execFwdPositionOps
· blocks 1
#6
0x6a65bb2a
#7
setData
#8
execOrders
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xfed09e59…a493
0x34b655…2a6f
4 touches
1 conflict
0x45d87399…4382
0x34b655…2a6f
4 touches
1 conflict
0x6e7d602f…590e
0x065c9d…c394
2 touches
0 conflicts
0x10ab9cff…2cbf
0x188d58…ea8e
2 touches
0 conflicts
0x10ab9cff…2cc0
0x188d58…ea8e
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x6237f1a7…2f59
0x3bd359…433a
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity