pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,959,198
← previous block
next block →
recent activity
Analyzing
Block #90,959,198
9 transactions · 8 stateful · 2026-07-28 04:11:44 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,959,198
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 2
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
0x6a682c78
#7
0x3f5c179b
#8
setData
#5
execFwdPositionOps
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x803eb45d…00bd
0x34b655…2a6f
4 touches
1 conflict
0x1c22eb60…d3e2
0x34b655…2a6f
4 touches
1 conflict
0xd793c15e…7dba
0x34b655…2a6f
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
2 touches
0 conflicts
0x147e9399…b7df
0x34b655…2a6f
2 touches
0 conflicts
0x31d88d27…7617
0x34b655…2a6f
2 touches
0 conflicts
0x474d11c3…3893
0x34b655…2a6f
2 touches
0 conflicts
0x4b2d9b6d…c213
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
0x803eb45df3…0100bd
Audit this contract →
← previous block
·
next block →
recent activity