pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,450,725
← previous block
next block →
recent activity
Analyzing
Block #90,450,725
9 transactions · 7 stateful · 2026-07-26 09:33:41 UTC
Parallelism
78
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,450,725
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
· blocks 1
#3
0x5a5d9a99
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 1
#7
setData
#8
execOrders
#2
0xab083028
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1781ea13…2f08
0x34b655…2a6f
4 touches
1 conflict
0x1bb624f3…c1b3
0x34b655…2a6f
4 touches
1 conflict
0x5fad6fee…7714
0x34b655…2a6f
4 touches
1 conflict
0x7bb46360…1f2b
0x34b655…2a6f
4 touches
1 conflict
0xc570d94d…6d86
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xda27c764…7fab
0x34b655…2a6f
4 touches
1 conflict
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
0x1781ea1353…952f08
Audit this contract →
← previous block
·
next block →
recent activity